From: James Bottomley <James.Bottomley@SteelEye.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] make file merging respect permissions
Date: Sat, 23 Apr 2005 16:37:02 -0400 [thread overview]
Message-ID: <1114288622.5228.1.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.58.0504231311300.2344@ppc970.osdl.org>
On Sat, 2005-04-23 at 13:17 -0700, Linus Torvalds wrote:
> The attached patch was seriously corrupt. Did you edit it by hand? The
> second chunk of the git-merge-one-file-script patch claims to have 12
> source lines, but only has 11, causing patch no end of confusion.
OK ... yes I admit it ... the shame ... I noticed a problem after I
generated it and then edited it in source
> I fixed up the line counts by hand, and the end result looked almost sane,
> but when looking closer, I noticed the
>
> + if [ $ -ne 0 ]; then
> + echo "ERROR: Leaving conflict merge in $src2"
> exit 1
>
> which just can't be right either ("$" never equals 0, so the above will
> always report an error), so I assume that whatever editing you did was
> really quite corrupt. Yeah, yeah, you obviously meant "$?", but the fact
> is, your patch is bogus, and I don't trust it. Can you re-send a valid one
> (and sign off on it).
Yes boss ... Just getting on a 'plane now. Should be able to send it
out in an hour or so.
James
next prev parent reply other threads:[~2005-04-23 20:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 18:22 [PATCH] make file merging respect permissions James Bottomley
2005-04-23 20:17 ` Linus Torvalds
2005-04-23 20:37 ` James Bottomley [this message]
2005-04-23 21:44 ` James Bottomley
2005-04-23 23:02 ` Petr Baudis
2005-04-23 23:09 ` James Bottomley
2005-04-23 23:21 ` James Bottomley
2005-04-24 1:01 ` Linus Torvalds
2005-04-24 4:42 ` James Bottomley
2005-04-24 4:55 ` Linus Torvalds
2005-04-24 5:03 ` James Bottomley
2005-04-24 5:05 ` [PATH] fix segfault in fsck-cache Andreas Gal
2005-04-24 5:24 ` Andreas Gal
2005-04-24 12:46 ` [PATCH] make file merging respect permissions 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=1114288622.5228.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).