git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: New special handing of '@' character broke my use case
Date: Wed, 14 Aug 2013 11:05:07 -0700	[thread overview]
Message-ID: <7vd2pgtagc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <520BC017.7050907@gmail.com> (Stefano Lattarini's message of "Wed, 14 Aug 2013 18:36:23 +0100")

Stefano Lattarini <stefano.lattarini@gmail.com> writes:

> My problems is that some new automagical interpretation of the bare
> @' character (introduced after 1.8.3) has destroyed my use case:
> ...
> I don't want to ask you to revert this new behaviour, but I'd like to
> at least have an option to disable it.

I do not think it is simply not worth the complexity to selectively
disable it.  If it is a regression, it is much better to simply
revert, if we can (it appears that cdfd9483 (Add new @ shortcut for
HEAD, 2013-05-07) can be reverted without any textual context, but
there may already be new stuff that depends on the "@").

For the upcoming release, I am very much tempted to revert it and
let the topic retried, by people who really want the "let's save
four keystrokes and replace it with @ aka Shift-<something>",
without hurting your use case (and others), after the upcoming
release.

What do others think?

  reply	other threads:[~2013-08-14 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 17:36 New special handing of '@' character broke my use case Stefano Lattarini
2013-08-14 18:05 ` Junio C Hamano [this message]
2013-08-14 19:20   ` Stefano Lattarini
2013-08-14 20:11   ` Johannes Sixt
2013-08-14 20:57     ` Junio C Hamano
2013-08-15  9:16       ` Stefano Lattarini
2013-08-14 18:20 ` 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=7vd2pgtagc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=stefano.lattarini@gmail.com \
    /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).