git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jonathan del Strother" <maillist@steelskies.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] don't mention index refreshing side effect in git-status docs
Date: Sun, 09 Dec 2007 10:15:51 -0800	[thread overview]
Message-ID: <7vhcirpwdk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 57518fd10712090816pa43cf97mbc1b8f5fbe81c66f@mail.gmail.com

"Jonathan del Strother" <maillist@steelskies.com> writes:

> ... the GIT-VERSION-GEN
> script occasionally gives me spurious 'dirty' results (eg when a file
> timestamp changes despite the content having changed).

Good eyes.  Either refreshing before diff-index or using the "git diff"
Porcelain would be more appropriate.

      reply	other threads:[~2007-12-09 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09  8:21 [PATCH] don't mention index refreshing side effect in git-status docs Jeff King
2007-12-09  8:33 ` Junio C Hamano
2007-12-09  8:42   ` Jeff King
2007-12-09 16:16 ` Jonathan del Strother
2007-12-09 18:15   ` Junio C Hamano [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:
  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=7vhcirpwdk.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=maillist@steelskies.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).