From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] diff-cache buglet
Date: Tue, 26 Apr 2005 11:22:31 -0700 [thread overview]
Message-ID: <7vsm1do0t4.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504261103550.18901@ppc970.osdl.org> (Linus Torvalds's message of "Tue, 26 Apr 2005 11:06:48 -0700 (PDT)")
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> Well, except for the fact that that isn't machine-readable
LT> either, since the "1 " thing might just be part of the
LT> filename..
Well, I somehow thought these things are in fixed column format;
mode, ->, sha, stage, and filename are all seperated with either
' ' or '\t'. So if I copy MN to "1 MN", presumably you would
see this:
100644 a716d58de4a570e0038f5c307bd8db34daea021f 0 MN
100644 a716d58de4a570e0038f5c307bd8db34daea021f 0 1 MN
So while I agree that // would also work, I fail to see why you
would even need that.
next prev parent reply other threads:[~2005-04-26 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 16:51 [RFC] diff-cache buglet Junio C Hamano
2005-04-26 17:11 ` Linus Torvalds
2005-04-26 17:56 ` Junio C Hamano
2005-04-26 18:06 ` Linus Torvalds
2005-04-26 18:22 ` Junio C Hamano [this message]
2005-04-26 18:38 ` Linus Torvalds
2005-04-26 18:56 ` Junio C Hamano
2005-04-26 19:09 ` Linus Torvalds
2005-04-26 20:34 ` Junio C Hamano
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=7vsm1do0t4.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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