From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Adeodato Simó" <dato@net.com.org.es>
Subject: Re: [PATCH] log: make --abbrev-commit's ellipsis configurable
Date: Fri, 13 Feb 2009 13:32:59 -0800 [thread overview]
Message-ID: <7vprhm81kk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1234529920-9694-1-git-send-email-trast@student.ethz.ch> (Thomas Rast's message of "Fri, 13 Feb 2009 13:58:40 +0100")
Thomas Rast <trast@student.ethz.ch> writes:
> 'git log --abbrev-commit' adds an ellipsis to all commit names that
> were abbreviated. This is annoying if you want to cut&paste the sha1
> from the terminal, since selecting by word will pick up '...' too.
> (And this cannot be fixed by making '.' a non-word character; in other
> instances, such as the '123457..abcdef0' from git-fetch, it's part of
> the expression.)
I actually think that it is a bug that --abbrev-commit uses ellipses.
It has been there since "diff --abbrev" was first introduced by commit
47dd0d5 (diff: --abbrev option, 2005-12-13). It did make sense to align
columns in abbreviated raw diff output with ellipses, but it did not make
much sense to do that for commit object names.
Some scripts might be relying on the presense of ellipses but depending on
the object distribution, the length of the ellipses can range from zero to
three; if they are expecting to always see three dots, such scripts are
already broken.
For this reason, I do not think it is necessarily a bad idea to make this
change even unconditionally to both plumbing and Porcelain.
next prev parent reply other threads:[~2009-02-13 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 12:58 [PATCH] log: make --abbrev-commit's ellipsis configurable Thomas Rast
2009-02-13 13:20 ` Johannes Schindelin
2009-02-13 13:37 ` Thomas Rast
2009-02-13 13:47 ` Johannes Schindelin
2009-02-13 14:24 ` [PATCH v2] " Thomas Rast
2009-02-13 15:32 ` Johannes Sixt
[not found] ` <m363jeux00.fsf@localhost.localdomain>
2009-02-13 16:45 ` Jakub Narebski
2009-02-13 19:27 ` [PATCH] " Jeff King
2009-02-13 21:32 ` Junio C Hamano [this message]
2009-02-13 22:10 ` [PATCH] log: do not print ellipses with --abbrev-commit Thomas Rast
2009-02-13 22:24 ` Jeff King
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=7vprhm81kk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dato@net.com.org.es \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.