Re: [Monotone-devel] Few remarks

[Christof Petig]

Jérôme Marant schrieb:
> Using hashes as revision IDs is definitely not user friendly.
> I know, it has already been mentioned in the FAQ, but even
> a simple ancestry graph can show that it is not really
> "human readable".
> IMHO, a simple database-wide per-commit autoincremented integer
> would be much nicer. It is even natural when using database,
> AFAIK and SQLite does this.

Most likely you are looking for something like this:

USAGE:
$ g++ monoshort.cc -o monoshort
$ ./monoshort "monotone --db /some/path/monotone.db" > short.sed

$ monotone log | sed --file short.sed | less
-----------------------------------------------------------------
Version: 2e0
Author: address@hidden
Date: 2004-11-20T15:58:05
ChangeLog:
[...]
$ monotone complete revision 2e0
2e0d044463ade95d106611197c09ce5c35cbfcee

Ancestry trees get quite readable with this script. (updated version to 
accomodate recent changes in 0.15)

Yours
   Christof

PS: Yes I know that the pipe is not implemented in the most efficient 
way (e.g. buffering). It simply fulfills my needs.

monoshort.cc.bz2
Description: application/bzip

signature.asc
Description: OpenPGP digital signature