public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Larry McVoy <lm@bitmover.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Problems using new Linux-2.4 bitkeeper repository.
Date: Sat, 16 Mar 2002 12:06:10 -0500	[thread overview]
Message-ID: <3C937B82.60500@mandrakesoft.com> (raw)
In-Reply-To: <200203161608.g2GG8WC05423@localhost.localdomain> <3C9372BE.4000808@mandrakesoft.com> <20020316083059.A10086@work.bitmover.com> <3C9375B7.3070808@mandrakesoft.com> <20020316085213.B10086@work.bitmover.com>

Larry McVoy wrote:

>On Sat, Mar 16, 2002 at 11:41:27AM -0500, Jeff Garzik wrote:
>
>>I started with Linus's linux-2.4 repo and so did Marcelo.  We 
>>independently checked in 2.4.recent patches (including proper renametool 
>>use), which included the ia64 and mips merges, which added a ton of 
>>files.  
>>
>
>OK, so there is the root cause.  It's time to talk about duplicate changes.
>
[...]

>There are things we can do in BK to deal with this, but they are not easy
>and are going to take several months, is my guess.  I'd like to see if you
>can work around this by avoiding duplicate patches.  If you can, do so, 
>you will save yourself lots of grief.
>
[...]

>You really want to listen to this, I'm trying to head you off from screwing
>up the history.  If you get 300 renames like this, it's almost always a 
>duplicate patch scenario.
>

I know why it happened, silly.

This was just an example of a real world example that actually happened, 
where BK sucked ass :)

Marcelo's BK tree did not exist when I created my marcelo-2.4 tree. 
 marcelo-2.4 repo existed for a while and people started using it.  Once 
Marcelo appeared with his "official" BK tree, people naturally want to 
migrate.  There were two migration paths: (1) export everything to GNU 
patches, or (2) click the mouse 300 times.

So, knowing that duplicate patches are a bad thing helps not in the 
least here...

    Jeff




  reply	other threads:[~2002-03-16 17:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  2:38 Problems using new Linux-2.4 bitkeeper repository James Bottomley
2002-03-15  4:55 ` Jeff Garzik
2002-03-16 16:08   ` James Bottomley
2002-03-16 16:28     ` Jeff Garzik
2002-03-16 16:30       ` Larry McVoy
2002-03-16 16:41         ` Jeff Garzik
2002-03-16 16:52           ` Larry McVoy
2002-03-16 17:06             ` Jeff Garzik [this message]
2002-03-16 17:14               ` Larry McVoy
2002-03-16 17:25                 ` Jeff Garzik
2002-03-16 17:38                   ` Larry McVoy
2002-03-16 17:51                     ` Jeff Garzik
2002-03-16 18:31                       ` Christer Weinigel
2002-03-16 18:05                     ` Jeff Garzik
2002-03-16 19:01                       ` Larry McVoy
2002-03-16 19:44                         ` Jeff Garzik
2002-03-17 10:49                 ` David Woodhouse
2002-03-17 15:54                   ` Larry McVoy
2002-03-17 16:23                   ` David Woodhouse
2002-03-17 18:15                     ` Larry McVoy
2002-03-17 18:34                     ` David Woodhouse
2002-03-18 15:25                       ` Tom Rini
2002-03-16 17:17             ` James Bottomley

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=3C937B82.60500@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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