I'm not all that certain if I'm using our new git repo in the prescribed way, but the simple patch below should fix the problem in a basic test I conducted. If you can confirm it, (ooh maybe even sign-off!) I'll get it into master, rel_2_0 and rel_2_1.
Hey Ben,
I'm not all that certain if I'm using our new git repo in the prescribed way, but the simple patch below should fix the problem in a basic test I conducted. If you can confirm it, (ooh maybe even sign-off!) I'll get it into master, rel_2_0 and rel_2_1.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=commit; h=ec45ea05739ec 350ed688fcf8e28 781e696819f4
Thanks