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 10:56:10 -0700 [thread overview]
Message-ID: <7vy8b5o211.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504261005360.18901@ppc970.osdl.org> (Linus Torvalds's message of "Tue, 26 Apr 2005 10:11:19 -0700 (PDT)")
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> I'm ok with that, but if so I think it should show the stage somehow, and
LT> make it clear that it's unmerged. Maybe by appending something to the name
LT> (maybe just a ':' and stage number, but I'd almost prefer the stage number
LT> to be translated into something human-readable, so maybe we could have
LT> something like
LT> filename.c^orig
LT> filename.c^first
LT> filename.c^second
LT> for stages 1-3 respectively)?
I'm the one who has been trying very hard to keep the output
machine readable (remember? many of the -z flags are mine).
While I agree with you that we should somehow show the stage, I
do not like your suggestion above very much. How about adding
one column for stage number before the filename when --unmerged
is given, just like show-files --stage shows? You'd soon get
used to the pattern that has a single digit in between
whitespaces to recognize which is merged and which isn't.
E.g. this is from show-files --stage:
100644 b258508afb7ceb449981bd9d63d2d3e971bf8d34 1 MM
100644 b431b272d829ff3aa4d1a5085f4394ab4d3305b6 2 MM
100644 19989d4559aae417fedee240ccf2ba315ea4dc2b 3 MM
100644 a716d58de4a570e0038f5c307bd8db34daea021f 0 MN
Another thing I'd like to rectify is that show-files use a space
while diff-tree and friends use a tab in between columns. Is it
too late to standardize one way or the other? My vote goes to
a space.
next prev parent reply other threads:[~2005-04-26 17:55 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 [this message]
2005-04-26 18:06 ` Linus Torvalds
2005-04-26 18:22 ` Junio C Hamano
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=7vy8b5o211.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