git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: git@vger.kernel.org
Subject: Re: [FEATURE-REQUEST] difftool --dir-diff: use the commit names as directory names instead of left/right
Date: Sat, 23 Mar 2013 16:30:18 +0100	[thread overview]
Message-ID: <1364052618.5363.5.camel@fermat.scientia.net> (raw)
In-Reply-To: <20130323123603.GL2283@serenity.lan>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On Sat, 2013-03-23 at 12:36 +0000, John Keeping wrote:
> > What do you all think about something like the output of
> > "git describe --always" instead of the SHA-1?
> I think Christoph was suggesting that it should use the revision as
> specified by the user, presumably falling back to HEAD when only one
> revision has been specified.
That was the idea... cause it has the best chance of being somehow
remembered/recognised by the user...
Taking any description, doesn't necessarily mean that the user has ever
seen this before or remembers it.



> I suspect in that case we have
> to be careful about special characters, perhaps it's best to just fall
> back to the SHA1 if we encounter something like
> "origin/master^{/^diff.c}" which is likely to cause issues with shell
> quoting.
Or maybe just pseudo-quote any such special characters by "_".
Otherwise,... one might have to many cases, where one falls back to the
SHA1... and looses a lot of the benefits.


Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5113 bytes --]

      reply	other threads:[~2013-03-23 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 16:52 [FEATURE-REQUEST] difftool --dir-diff: use the commit names as directory names instead of left/right Christoph Anton Mitterer
2013-03-23  4:56 ` David Aguilar
2013-03-23 12:36   ` John Keeping
2013-03-23 15:30     ` Christoph Anton Mitterer [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=1364052618.5363.5.camel@fermat.scientia.net \
    --to=calestyo@scientia.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;
as well as URLs for NNTP newsgroup(s).