Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Toru Okugawa <>
To: Junio C Hamano <>
Cc: Eric Sunshine <>,
Subject: Re: Re* Unexpected behavior with the rev-parse operation
Date: Wed, 1 May 2024 13:55:44 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <xmqqedamzo17.fsf@gitster.g>

On Wed, May 1, 2024 at 3:46 AM Junio C Hamano <> wrote:
> When you write a script that you might want to use as a part of a
> hook, for example, you may end up running it inside .git/ and it may
> be necessary (depending on what the script does and how it is
> written) to tell where you are in the working tree (or if you are in
> the working tree in the first place).

I misunderstood the purpose of the option initially, but now I
understand it. Thank you for your explanation.

      reply	other threads:[~2024-05-01  4:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 13:58 Unexpected behavior with the rev-parse operation Toru Okugawa
2024-04-28 18:08 ` Eric Sunshine
2024-04-28 23:07   ` Re* " Junio C Hamano
2024-04-30 14:26     ` Toru Okugawa
2024-04-30 18:46       ` Junio C Hamano
2024-05-01  4:55         ` Toru Okugawa [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).