Re: [fossil-users] Manifest files
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, like the recent ci-comment change. i've never personally needed them in a source tree, other than to make sure i don't include them in distribution tarballs. (i.e., they get in my way every now and then.) Rather than create_manifest, i would recommend: manifest print // dump to stdout manifest uuid // dump only manifest.uuid to stdout manifest create // creates manifest + manifest.uuid :-? -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Path Separators
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 path/to/file from the output into the next command, perhaps fossil gdiff. Obviously, on Windows, this fails. And it's a hassle to have to edit the path separators every time. How do other Win/Fossil users handle this? Would it make sense to change Fossil to output backslashes as the path separator on Windows platforms (path\to\file)? Has this already been discussed? Thanks! -Clark ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Path Separators
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, then wanting to copy/paste a path/to/file from the output into the next command, perhaps fossil gdiff. Obviously, on Windows, this fails. And it's a hassle to have to edit the path separators every time. How do other Win/Fossil users handle this? Would it make sense to change Fossil to output backslashes as the path separator on Windows platforms (path\to\file)? Has this already been discussed? Thanks! -Clark Easy workaround unless/until fossil is changed would be to use the http://www.cygwin.com/ bash shell. -- Daniel JB Clark | Sys Admin, Free Software Foundation pobox.com/~dclark | http://www.fsf.org/about/staff#danny ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Manifest files
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 generated by a fossil command: fossil create_manifest Good idea. Or even stuffed in the DB, like the recent ci-comment change. i've never personally needed them in a source tree, other than to make sure i don't include them in distribution tarballs. (i.e., they get in my way every now and then.) Rather than create_manifest, i would recommend: manifest print // dump to stdout manifest uuid // dump only manifest.uuid to stdout manifest create // creates manifest + manifest.uuid :-? -- - stephan beal http://wanderinghorse.net/home/stephan/ I thought Richard answered that (in the message the one you answered was an answer to!). Seems the only way to keep everyone happy would be to make it another repository option. Eric ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
