git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ryicoh <ryicoh@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, gitgitgadget@gmail.com, ryicoh@gmail.com
Subject: Re: [PATCH] doc: add that '-' is the same as '@{-1}'
Date: Sun,  2 Apr 2023 00:53:42 +0900	[thread overview]
Message-ID: <20230401155342.21230-1-ryicoh@gmail.com> (raw)
In-Reply-To: <xmqqlejchpct.fsf@gitster.g>

Hi Oswald, Junio and Phillip.

Thank you for your reviews. Let me reply to each comments.

> i'd recommend quoting the dash as you do in the summary (or adding some markup?), as otherwise it's way too easy to misread.

That's good. I'll fix it.

> It is certainly *not* synonymous in general and I
> doubt we want to make it to.

That's correct. Your examples helped me understand.

> A few commands (checkout, merge, rebase and switch spring to mind) accept '-' as a shorthand for '@{-1}' but I don't think it is universally accepted.

That's correct too.


> for now we should
> update its documentation to mention "- can also be used in place of
> @{-1}".

Finally, How should I update the documentation? How about following changes?

- You may also specify `-` which is synonymous to `@{-1}`.
+ Only some commands (checkout, switch, etc,), you may also specify `-` which is synonymous to `@{-1}`.

Other commands also seem to accept '-', such as `cherry-pick`.
It's not good idea to write all commands that accepted it.

Best Wishes


  reply	other threads:[~2023-04-01 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 10:11 [PATCH] doc: add that '-' is the same as '@{-1}' ryicoh via GitGitGadget
2023-03-31 12:03 ` Oswald Buddenhagen
2023-03-31 16:12 ` Junio C Hamano
2023-04-01 15:53   ` ryicoh [this message]
2023-04-02 12:26     ` Junio C Hamano
2023-03-31 16:29 ` Phillip Wood

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=20230401155342.21230-1-ryicoh@gmail.com \
    --to=ryicoh@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.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).