linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, linux-kernel@vger.kernel.org
Subject: Re: Htree directory index for Ext2, updated
Date: Wed, 22 May 2002 11:43:18 +0200	[thread overview]
Message-ID: <E17ASeO-0001xB-00@starship> (raw)
In-Reply-To: <200205170736.g4H7aNj281162@saturn.cs.uml.edu> <E178xSu-0000Dc-00@starship> <20020518172634.GK21295@turbolinux.com>

On Saturday 18 May 2002 19:26, Andreas Dilger wrote:
> On May 18, 2002  08:13 +0200, Daniel Phillips wrote:
> > I cloned a repository that is arranged like:
> > 
> >   somedir
> >     |
> >     |--linux
> >     |    |
> >     |    The usual stuff
> >     |
> >      `---other things
> > 
> > Bitkeeper wants the destination for the import to be 'somedir', and
> > cannot figure out how to apply a patch that looks like:
> > +++ src/include/linux/someheader.h, for instance.
> 
> And that is bad in what way?

It is bad in that there is no way to import the patch into BitKeeper.

> If you try to apply that patch from
> 'somedir' you expect patch/BK to have ESP to know it should apply
> under 'linux'.  If 'patch' will apply such a diff, then it is just
> a sign of the problems you were complaining about - that it uses
> heuristics to guess which file to modify, and they are not 100% right.
> 
> Of course, if you are really talking about a patch, and not a BK
> changeset, then the problem lies solely with 'patch' and 'diff'
> and has nothing to do with BK at all.

It looks like a hole in BitKeeper.  How do you suggest I apply my
perfectly normal patch?

-- 
Daniel

  reply	other threads:[~2002-05-22  9:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17  0:34 Htree directory index for Ext2, updated Daniel Phillips
2002-05-17  4:22 ` Albert D. Cahalan
2002-05-17  5:18   ` Daniel Phillips
2002-05-17  7:36     ` Albert D. Cahalan
2002-05-18  1:21       ` Daniel Phillips
2002-05-18  5:34         ` Andreas Dilger
2002-05-18  5:44           ` Daniel Phillips
2002-05-18  5:57             ` Kai Germaschewski
2002-05-18  5:58             ` Andreas Dilger
2002-05-18  6:13               ` Daniel Phillips
2002-05-18 17:26                 ` Andreas Dilger
2002-05-22  9:43                   ` Daniel Phillips [this message]
2002-05-22 10:23                     ` Andreas Dilger
2002-05-22 14:40                       ` Larry McVoy
2002-05-18  6:22               ` Daniel Phillips
2002-05-17  7:43     ` Russell King
2002-05-18  0:49       ` Daniel Phillips

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=E17ASeO-0001xB-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=acahalan@cs.uml.edu \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).