On Wed, Nov 20, 2013 at 6:42 AM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Thus said "John L. Poole" on Tue, 19 Nov 2013 05:12:08 -0800: > > The reason I'm writing to this list is to inquire if there will be a > > new release coming shortly or if I should try to create an ebuild > > that incorporates the patch that fixes this problem? > > I think it would be safest just to wait for the next release. Here are > some issues you'll need to consider if you go the patch route: > ... 3) To avoid 2, you can merge/commit the patch into a private branch in > a cloned copy of the fossil repository. Then extract the patch from > there as a diff from the official released version and your branch. > Good morning! If the patch is relatively small, please just paste it to the list (don't attach it - attachments get stripped). i don't see the prior mail explaining the problem - maybe it already contains the patch? I don't know when the next official release will be, but this will give > you an idea of the historical trend: > Nobody knows - historically we release them when the changelog gets "unusually long" or when something truly critical was fixed. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
