On Mon, Jul 22, 2013 at 5:52 PM, j. van den hoff <veedeeh...@googlemail.com>wrote:
> unambiguous sequential numbering of all checkins (just like `hg' has > always been doing it: checkins are denoted by something like > 10:0cb3d1256b... where the `10' is the locally valid incremental index of > the checkin which can be used instead of the sha1 hash in all commands). > one obvious example being inspection of diffs between consecutive checkins. > We could probably use the local db record IDs for that purpose. They might be 3-5 digits and not necessarily incremented in steps of one (because blobs are used for various purposes), but they would be sequential in time (at least in theory). > as would be a facility to get the complete timeline output without having > to guess/enter a sufficiently large number for the `-n' flag.... > The simplest change would be for it to interpret negative values as "unlimited", and maybe add a --reverse flag so that --reverse -n -1 would show only the first checkin? > and of course `grep'. > There is some code for this but it only looks in local files, so it's just a glorified (and platform-neutral) version of the /usr/bin/grep. In any case, i've added a section on "search" to the doc. i'm off of work starting Wednesday and will attempt to set up a skeleton app where we can start prototyping/experimenting (while making no sort of commitments). It occurred to me today that the command line arg processing is app-level, not lib-level, and there's lots of "pre-work" i can do there without having any concrete details about the library. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
