From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] diff: --abbrev option
Date: Sat, 17 Dec 2005 18:57:19 -0800 [thread overview]
Message-ID: <7vek4byuwg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051218001756.GS22159@pasky.or.cz> (Petr Baudis's message of "Sun, 18 Dec 2005 01:17:56 +0100")
Petr Baudis <pasky@suse.cz> writes:
> I was actually thinking to by default trim all the hashes Cogito show
> to 12 or 16 characters. Seven still seems dangerously low to me, though;
> it would be nice if the number of characters to trim would be
> configurable (unless I've missed that).
Well, I did better than you imagined this time, for a change ;-)
It trims and adds extra as needed without breaking alignments,
so you could get something like this:
> :100755 100755 0266f46... b0e54ed... M git-branch.sh
> :100755 100755 f241d4b9.. 36308d2ab. M git-checkout.sh
That is, ... is not just distraction but are part of the
design. Cut and paste is a byproduct.
next prev parent reply other threads:[~2005-12-18 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 9:41 [PATCH] diff: --abbrev option Junio C Hamano
2005-12-18 0:17 ` Petr Baudis
2005-12-18 2:57 ` Junio C Hamano [this message]
2005-12-18 11:45 ` Petr Baudis
2005-12-18 18:35 ` 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=7vek4byuwg.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@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