git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "ryicoh via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: ryicoh <ryicoh@gmail.com>, ryicoh <ryicoh@gmail.com>
Subject: [PATCH] doc: add that '-' is the same as '@{-1}'
Date: Fri, 31 Mar 2023 10:11:43 +0000	[thread overview]
Message-ID: <pull.1484.git.git.1680257503697.gitgitgadget@gmail.com> (raw)

From: ryicoh <ryicoh@gmail.com>

Signed-off-by: ryicoh <ryicoh@gmail.com>
---
    doc: add that '-' is the same as '@{-1}'
    
    Now, the document of '-' is written only git-switch.txt.
    
    https://github.com/git/git/blob/6369acd968d02899973a9a853c48029b92cea401/Documentation/git-switch.txt#L51
    
    I want same one in revisions.txt.
    
    Thank you.

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1484%2Fryicoh%2Fdoc-hyphen-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1484/ryicoh/doc-hyphen-v1
Pull-Request: https://github.com/git/git/pull/1484

 Documentation/revisions.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 9aa58052bc7..9e7ea2cf71e 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/revisions.txt
@@ -94,7 +94,8 @@ some output processing may assume ref names in UTF-8.
 
 '@{-<n>}', e.g. '@{-1}'::
   The construct '@{-<n>}' means the <n>th branch/commit checked out
-  before the current one.
+  before the current one. You may also specify - which is synonymous
+  to @{-1}.
 
 '[<branchname>]@\{upstream\}', e.g. 'master@\{upstream\}', '@\{u\}'::
   A branch B may be set up to build on top of a branch X (configured with

base-commit: 6369acd968d02899973a9a853c48029b92cea401
-- 
gitgitgadget

             reply	other threads:[~2023-03-31 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 10:11 ryicoh via GitGitGadget [this message]
2023-03-31 12:03 ` [PATCH] doc: add that '-' is the same as '@{-1}' Oswald Buddenhagen
2023-03-31 16:12 ` Junio C Hamano
2023-04-01 15:53   ` ryicoh
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=pull.1484.git.git.1680257503697.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ryicoh@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).