From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: [9fans] hgfs
Date: Mon, 27 Jun 2011 07:43:17 +0200 [thread overview]
Message-ID: <71268cb43521baf565533fb50f5596ef@gmx.de> (raw)
forgot the mention some bits:
hgfs gives you one directory per revision. a revision dir
looks like this:
cpu% cd /n/hg/99
cpu% ls -l
d-r-xr-xr-x M 37623 stanley.lieber hgfs 0 Apr 17 22:19 changes
d-r-xr-xr-x M 37623 stanley.lieber hgfs 0 Apr 17 22:19 files
--r--r--r-- M 37623 stanley.lieber hgfs 157 Apr 17 22:19 log
--r--r--r-- M 37623 stanley.lieber hgfs 16 Apr 17 22:19 rev1
--r--r--r-- M 37623 stanley.lieber hgfs 0 Apr 17 22:19 rev2
--r--r--r-- M 37623 stanley.lieber hgfs 25 Apr 17 22:19 who
--r--r--r-- M 37623 stanley.lieber hgfs 56 Apr 17 22:19 why
files/ contains the whole snapshot.
changes/ is like files, but contains only the files that where
changed in that revision.
log is the raw mercurial changelog entry.
rev1 and rev2 contain the directory names of the parent revisions.
the "who" file contains the commiter and "why" the commit message.
i'm thinking about providing some history(1) like rc scripts that
help with some daily tasks.
any suggestions and ideas are welcome.
source:
/n/sources/contrib/cinap_lenrek/hgfs.tgz
http://9hal.ath.cx/usr/cinap_lenrek/hgfs.tgz
--
cinap
next reply other threads:[~2011-06-27 5:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 5:43 cinap_lenrek [this message]
2011-06-27 13:15 ` hiro
-- strict thread matches above, loose matches on Subject: below --
2014-05-22 6:52 Skip Tavakkolian
2014-05-22 7:36 ` lucio
2014-05-22 9:54 ` Aram Hăvărneanu
2014-05-22 10:30 ` lucio
2014-05-22 10:41 ` Aram Hăvărneanu
2014-05-22 15:35 ` Skip Tavakkolian
2014-05-22 15:56 ` erik quanstrom
2014-05-22 16:17 ` ron minnich
2014-05-22 16:21 ` Kurt H Maier
2014-05-22 16:31 ` Aram Hăvărneanu
2014-05-22 18:37 ` ron minnich
2014-05-22 18:45 ` Kurt H Maier
2014-05-22 18:51 ` Aram Hăvărneanu
2014-05-22 19:02 ` Latchesar Ionkov
2014-05-22 19:13 ` Kurt H Maier
2014-05-22 19:16 ` erik quanstrom
2014-05-22 19:23 ` Latchesar Ionkov
2014-05-23 3:45 ` hiro
2014-05-22 19:11 ` Skip Tavakkolian
2014-05-22 19:23 ` Bakul Shah
2014-05-22 19:47 ` Skip Tavakkolian
2014-05-22 16:20 ` lucio
2014-05-22 19:46 ` Bakul Shah
2011-06-27 5:09 cinap_lenrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71268cb43521baf565533fb50f5596ef@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).