Re: [PATCH 1/2] test for '!' handling in rev-parse's named commits

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 4, 2015, 17:09 UTC
Message-ID: <xmqqy4jzv1ry.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CAAKF_uYrjBsVY8YOmRtMU8jB5rA57r+-N_KboqwWL3YRRqeKAg@mail.gmail.com>

Will Palmer <wmpalmer@gmail.com> writes:

> What I'm thinking now is that "@^{/foo}" can be thought of as a
> potential "shorthand-form" of what could be "@^{/!(m=foo)}", in which
> case "@^{/!-foo}" could similarly be thought of as a potential
> shorthand-form of what could be "@^{/!(m-foo)}".

Ah, our messages crossed, it seems. Yes, I think we are on the same page, and it is sensible to think of "/!-string" as a short-hand for the more complete syntax that uses descriptive word, not mnemonic, e.g. "/!(unmatch=string)", that the old thread envisioned.

I think it is OK (and probably preferrable) to start with only "/!-string" without the long-hand, as we do not know how multiple long-hand instructions should interact with each other.

Thanks.