I downloaded the lastest Windows fossil build tonight and am giving DVCS
another shot. Some notes:
1. I like the fact that I could --date-override the initial create date
stamp.
1a. I wish that I could --date-override a commit at the command line so
that I didn't have to edit the date stamp via
On Friday, August 24, 2012 10:35 PM, Richard Hipp wrote:
Fossil keeps track of which files have changed (by default) by looking
at the file size and the mtime. If neither the file size nor the mtime
have changed, fossil (by default) assumes that the content of the file
is also unchanged.
Ah, then perhaps my first edit will be to document the undocumented rather
than implement the unimplemented. :) To answer your question, yes I am
converting a smallish multipurpose svn repository I've been using for about
three years. It has multiple projects in it that I don't want to all
migrate
Thanks for the info. I was going to tackle that myself today so that I
could get that benefit, and appreciate the pointers. Of course, submitting
it (along with eventual paperwork) gives me 'practical experience' with
pushing stuff back to a master repo (where my current personal project
needs
On Sat, Aug 25, 2012 at 10:25 AM, Scott Robison sc...@scottrobison.uswrote:
As for the color coding, I was not referring to branch colors, I was
referring to colors used to highlight bullet characters in an admin/config
page.
That whole colored-dot thing on the users page is hokey and needs
I'm not much of a visual/ui design guy but I'll see what I can come up with.
SDR
On Aug 25, 2012 9:09 AM, Richard Hipp d...@sqlite.org wrote:
On Sat, Aug 25, 2012 at 10:25 AM, Scott Robison sc...@scottrobison.uswrote:
As for the color coding, I was not referring to branch colors, I was
6 matches
Mail list logo
