2012/12/1 Richard Hipp <[email protected]>:
>> I would very much like to see this going into the upcoming 1.25
>> release. Is it scheduled to get merged back into trunk?
>
>
> No. This adds complication to a code base that is complicated enough
> already. It is vitally important to keep Fossil as simple as possible, in
> order to promote reliability and longevity. There are no plans to merge this
> branch.
I agree with Richard on this. The most important part of the patch is
already on trunk now: allowing '[', ']', '"', '*' and '?' in filenames. The
added value of the remaining part is minimal: It would make the
win32 build of fossil do the same as the cygwin build of fossil.
So, you have the functionality already: Just build fossil.exe
for cygwin, it does exactly the same.
That's not sufficient excuse to rush it into 1.25. And missing is
still a test-case description of exactly what is the added value:
What can you do with the changed version what cannot be
done with the trunk version.
Thanks!
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
