On Fri, Dec 18, 2009 at 9:42 AM, Benjohn Barnes benj...@fysh.org wrote:
Ah, that's cool to know. I'd wondered what they were for too. Would it
be possible / sensible to make them optional, or generated by a fossil
command:
fossil create_manifest
Good idea. Or even stuffed in the DB,
I'm using Fossil on MS Windows under the TCC/4NT shell, and am mostly really
happy with it. But the one thing that causes me the most problems is the
forward slash path separator in the output from many fossil commands.
I often find myself using fossil status, then wanting to copy/paste a
Clark Christensen wrote:
I'm using Fossil on MS Windows under the TCC/4NT shell, and am mostly really
happy with it. But the one thing that causes me the most problems is the
forward slash path separator in the output from many fossil commands.
I often find myself using fossil status,
From: Stephan Beal sgb...@googlemail.com
Date: Fri, December 18, 2009 10:07 am
On Fri, Dec 18, 2009 at 9:42 AM, Benjohn Barnes benj...@fysh.org wrote:
Ah, that's cool to know. I'd wondered what they were for too. Would it
be possible / sensible to make them optional, or
4 matches
Mail list logo