From: Theodore Ts'o <tytso@mit.edu>
To: Christopher Li <hg@chrisli.org>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com,
Mercurial List <mercurial@selenic.com>
Subject: Re: bitkeeper gone in 2 weeks - which RCS?
Date: Thu, 16 Jun 2005 07:36:54 -0400 [thread overview]
Message-ID: <20050616113654.GA10969@thunk.org> (raw)
In-Reply-To: <20050615230320.GB10613@64m.dyndns.org>
On Wed, Jun 15, 2005 at 07:03:20PM -0400, Christopher Li wrote:
> > Agreed. I've never really used the "different commit
> > comment per file" thing in bitkeeper. Well, I used it
> > in the beginning, but I stopped using it after I found
> > out that "bk changes" didn't actually show them anyway!
> >
>
> For one thing, it has performance implication of open every single
> file to get that per-file change log if you run the change history.
> I am still not convince the per file change log is very useful
> feature. Having more place to look is not always a good thing.
I wouldn't necessarily want to see the per-file change logs when
looking at the change history. It's for when you want to dive into
the sources and do a more detailed look into a single changeset, or
when looking at the revision history for a particular file. (i.e.,
when looking at the file revisions history in hg-web).
- Ted
next prev parent reply other threads:[~2005-06-16 11:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 22:11 bitkeeper gone in 2 weeks - which RCS? Ian Pratt
2005-06-16 1:16 ` Matt Mackall
2005-06-16 1:21 ` Rik van Riel
2005-06-15 23:03 ` Christopher Li
2005-06-16 11:36 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 0:16 Soh Tk-r28629
2005-06-21 0:29 ` Matt Mackall
2005-06-15 21:35 Ian Pratt
2005-06-15 21:45 ` Andrew Thompson
2005-06-16 2:56 ` Rusty Russell
[not found] ` <mailman.1118871375.26501@unix-os.sc.intel.com>
2005-06-16 18:34 ` Arun Sharma
2005-06-20 20:39 ` Paul Larson
2005-06-20 20:44 ` Rik van Riel
2005-06-20 20:54 ` Josh Triplett
2005-06-20 21:01 ` Andrew Thompson
2005-06-20 21:28 ` Paul Larson
[not found] ` <mailman.1119300279.12847@unix-os.sc.intel.com>
2005-06-20 21:03 ` Arun Sharma
2005-06-20 21:08 ` Rik van Riel
2005-06-15 19:45 Ian Pratt
2005-06-15 20:10 ` Rik van Riel
2005-06-14 19:09 Rik van Riel
2005-06-14 19:26 ` Paul Larson
2005-06-14 19:27 ` Ronald G. Minnich
[not found] ` <mailman.1118777276.15947@unix-os.sc.intel.com>
2005-06-14 19:43 ` Arun Sharma
2005-06-14 19:50 ` Paul Larson
2005-06-14 19:58 ` Arun Sharma
2005-06-14 23:31 ` aq
2005-06-14 23:50 ` Rusty Russell
2005-06-15 7:09 ` Michael Paesold
2005-06-16 2:37 ` Ronald G. Minnich
2005-06-16 11:51 ` David Hopwood
2005-06-15 19:18 ` Rik van Riel
2005-06-14 19:52 ` Ronald G. Minnich
2005-06-14 19:54 ` Arun Sharma
2005-06-15 7:51 ` Gerd Knorr
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=20050616113654.GA10969@thunk.org \
--to=tytso@mit.edu \
--cc=hg@chrisli.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mercurial@selenic.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.