Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff: --abbrev option
Date: Sun, 18 Dec 2005 12:45:22 +0100	[thread overview]
Message-ID: <20051218114522.GW22159@pasky.or.cz> (raw)
In-Reply-To: <7vek4byuwg.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Sun, Dec 18, 2005 at 03:57:19AM CET, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> 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.

Ok, that's nice! :-) And if I'm going to machine-process this later,
I can just trim the trailing dots anyway. And it seems that I can give
--abbrev a number argument to specify the minimal abbreviation, even
cooler! :-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

  reply	other threads:[~2005-12-18 11:46 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
2005-12-18 11:45     ` Petr Baudis [this message]
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=20051218114522.GW22159@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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