public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Tom Lord <lord@regexps.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel SCM: When does CVS fall down where it REALLY matters?
Date: Mon, 11 Mar 2002 09:10:31 -0800	[thread overview]
Message-ID: <20020311091031.O26447@work.bitmover.com> (raw)
In-Reply-To: <200203092222.OAA03372@morrowfield.home>
In-Reply-To: <200203092222.OAA03372@morrowfield.home>; from lord@regexps.com on Sat, Mar 09, 2002 at 02:22:33PM -0800

On Sat, Mar 09, 2002 at 02:22:33PM -0800, Tom Lord wrote:
>        $ bk mv old new 
> 
>        No danger, no drawbacks, no hand editing of history files. 
> 
> I like the arch way of renaming a file:
> 
> 	$ mv old new
> 
> (Yes, history is preserved, etc.)

Come on, Tom, truth in advertising.  If you don't have the file identifier 
in the file, what you just described doesn't work.

Arch has a concept of an "inode" quite similar to BitKeeper, in fact
one wonders where the idea came from :-), and as long as the the "inode"
is embedded in the file, you can do what Tom says above.  If it isn't,
that won't work, no matter what he says.  I speak from the experience
of importing lots of kernel versions into BK and trying to automate the
detection of renames.  Can't be done and if Tom claims it can, then 
ask him to demonstrate how by taking a a few thousand kernel patches
and autodetecting the renames.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-03-11 17:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 22:22 Kernel SCM: When does CVS fall down where it REALLY matters? Tom Lord
2002-03-11 17:10 ` Larry McVoy [this message]
2002-03-12  6:09   ` Tom Lord
  -- strict thread matches above, loose matches on Subject: below --
2002-03-07 23:51 Jonathan A. George
2002-03-07 23:59 ` Rik van Riel
2002-03-08  0:03   ` Cort Dougan
2002-03-09 11:17     ` Roman Zippel
2002-03-09 16:45       ` Kurt Roeckx
2002-03-08  0:26   ` Andrew Morton
2002-03-08  0:36     ` Rik van Riel
2002-03-08  1:48     ` Neil Brown
2002-03-10 20:27       ` Pavel Machek
2002-03-11 21:11         ` Rik van Riel
2002-03-12 16:31           ` Pavel Machek
2002-03-08  7:37     ` Alex Riesen
2002-03-08  0:29   ` Jonathan A. George
2002-03-08  0:43     ` Rik van Riel
2002-03-08  9:32       ` Pau Aliagas
2002-03-08 16:37         ` Rik van Riel
2002-03-08 20:15           ` Pau Aliagas
2002-03-08 20:22             ` Rik van Riel
2002-03-08 20:28               ` Pau Aliagas
2002-03-08  0:38   ` Erik Andersen
2002-03-08  9:38     ` Pau Aliagas
2002-03-09  1:52     ` Val Henson
2002-03-09  2:00       ` Mike Fedyk
2002-03-09  2:25       ` Dave Jones
2002-03-08  1:19   ` Dave Jones
2002-03-08 20:27     ` Jonathan A. George
2002-03-08 21:59       ` Eli
2002-03-08  3:15   ` H. Peter Anvin
2002-03-08  9:39     ` Pau Aliagas
2002-03-11 17:05   ` Larry McVoy
2002-03-11 17:12     ` Randy.Dunlap
2002-03-11 17:25       ` Larry McVoy
2002-03-11 17:53       ` Jonathan A. George
2002-03-11 18:03         ` Larry McVoy
2002-03-11 20:36     ` Rik van Riel
2002-03-11 21:01       ` Larry McVoy
2002-03-11 21:28         ` Rik van Riel
2002-03-10 19:28 ` Pavel Machek

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=20020311091031.O26447@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@regexps.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox