From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff: --abbrev option
Date: Sun, 18 Dec 2005 10:35:01 -0800 [thread overview]
Message-ID: <7v4q56qmne.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051218114522.GW22159@pasky.or.cz> (Petr Baudis's message of "Sun, 18 Dec 2005 12:45:22 +0100")
Petr Baudis <pasky@suse.cz> writes:
> 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! :-)
Well, it is not for machine consumption to begin with anyway.
It is an optional toy ;-).
prev parent reply other threads:[~2005-12-18 18:35 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
2005-12-18 18:35 ` Junio C Hamano [this message]
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=7v4q56qmne.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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