From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>, git@vger.kernel.org
Subject: Re: New special handing of '@' character broke my use case
Date: Wed, 14 Aug 2013 22:11:20 +0200 [thread overview]
Message-ID: <520BE468.1030808@kdbg.org> (raw)
In-Reply-To: <7vd2pgtagc.fsf@alter.siamese.dyndns.org>
Am 14.08.2013 20:05, schrieb Junio C Hamano:
> 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?
Stefano's use-case, where @/foo is turned into HEAD/foo, indicates a bug.
In my opinion, the topic, which touches a central part of ref handling,
was a bit hurried (and this report is a symptom of it), and I wouldn't
mind seeing it reverted.
-- Hannes
next prev parent reply other threads:[~2013-08-14 20:11 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
2013-08-14 19:20 ` Stefano Lattarini
2013-08-14 20:11 ` Johannes Sixt [this message]
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=520BE468.1030808@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).