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: Sat, 18 May 2002 08:13:16 +0200 [thread overview]
Message-ID: <E178xSu-0000Dc-00@starship> (raw)
In-Reply-To: <200205170736.g4H7aNj281162@saturn.cs.uml.edu> <E178x1B-0000DW-00@starship> <20020518055808.GH21295@turbolinux.com>
On Saturday 18 May 2002 07:58, Andreas Dilger wrote:
> On May 18, 2002 07:44 +0200, Daniel Phillips wrote:
> > Funny you should mention that, since Bitkeeper has embarrassed itself pretty
> > badly with respect to patches, so far.
> >
> > - Somebody decided to add another level on top of the linux root directory
> > in their source directory. I can't import patches into that.
>
> Hmm, I'm not sure what you are referring to here.
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.
--
Daniel
next prev parent reply other threads:[~2002-05-18 6:13 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 [this message]
2002-05-18 17:26 ` Andreas Dilger
2002-05-22 9:43 ` Daniel Phillips
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=E178xSu-0000Dc-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).