Case sensitivity does not work for directory names, only for filenames.
-Original Message-
From: to...@acm.org
Last change with case sensitivity for Windows works great.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Sat, Oct 18, 2014 at 5:37 AM, to...@acm.org wrote:
Case sensitivity does not work for directory names, only for filenames.
Please try again with the latest.
Are we ready to merge this enhancement into trunk? Are there any
objections to the new command-line timeline capability?
--
D.
On Sat, Oct 18, 2014 at 06:36:08AM -0400, Richard Hipp wrote:
On Sat, Oct 18, 2014 at 5:37 AM, to...@acm.org wrote:
Case sensitivity does not work for directory names, only for filenames.
Please try again with the latest.
I re-test everything I could think off with the latest,
On Sat, 18 Oct, Richard Hipp wrote:
Are we ready to merge this enhancement into trunk? Are there any
objections to the new command-line timeline capability?
I see a regression regarding previous behaviour.
Our scripts use the following two-step process in order to see the
timeline of a
That's because 'trunk' is incorrectly interpreted as filename.
This is related to the same problem I have already reported about filenames
having priority over internal keywords and tags, instead of the other way
around.
I suspect it will be fixed soon.
-Original Message-
From:
On Fri, Oct 17, 2014 at 11:47:53PM +0300, to...@acm.org wrote:
OK, here's one more minor issue you can easily test with sqlite3
repo under Windows. Windows filenames are case insensitive. Trying
with wrong case
snip
This one is fixed now too..
--
Martin G.
Again, thanks for the quick fix regarding forced -t ci on filename. Works
perfectly. As far as I can tell this new feature is complete! Great work!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
7 matches
Mail list logo
