From: Andreas Dilger <adilger@clusterfs.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, linux-kernel@vger.kernel.org
Subject: Re: Htree directory index for Ext2, updated
Date: Fri, 17 May 2002 23:58:08 -0600 [thread overview]
Message-ID: <20020518055808.GH21295@turbolinux.com> (raw)
In-Reply-To: <200205170736.g4H7aNj281162@saturn.cs.uml.edu> <E178suL-0000Bs-00@starship> <20020518053458.GF21295@turbolinux.com> <E178x1B-0000DW-00@starship>
On May 18, 2002 07:44 +0200, Daniel Phillips wrote:
> On Saturday 18 May 2002 07:34, Andreas Dilger wrote:
> > On May 18, 2002 03:21 +0200, Daniel Phillips wrote:
> > > Patch is severely broken in its current form, not only for the
> > > reasons you stated, but also because of its inability to handle
> > > renaming in any sane way. I want a patch --sane option.
> >
> > I bet BitKeeper gets it right... ;-) ;-) ;-)
>
> 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 can apply patches to bitkeeper repository using the normal 'patch',
> but Bitkeeper gets its revenge later, as each bk edit command starts
> off by throwing away the patch.
This is also strange, as when I use patch to apply a patch to files not
checked out, patch asks me if I should check them out in write mode
(which I do, of course).
Of course, if you are using patch to apply changes to a BK tree it isn't
really BK in the end. What I was referring to was importing a changeset
would probably get the target files correct 100% of the time, unlike the
situation you are describing with patch.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-05-18 6:00 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 [this message]
2002-05-18 6:13 ` Daniel Phillips
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=20020518055808.GH21295@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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).