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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 23 2002 - 22:00:24 EST