From: Junio C Hamano <gitster@pobox.com>
To: "Peter Valdemar Mørch" <4ux6as402@sneakemail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Teach git log --check to return an appropriate error code
Date: Sat, 09 Aug 2008 11:58:50 -0700 [thread overview]
Message-ID: <7vljz66mmt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1218265054-19220-1-git-send-email-4ux6as402@sneakemail.com> (Peter Valdemar Mørch's message of "Sat, 9 Aug 2008 08:57:34 +0200")
Peter Valdemar Mørch <4ux6as402@sneakemail.com> writes:
> The return value is a bitfield, with |= 1 if HAS_CHANGES
> (clearly log has changes "always" - except e.g. "git log
> HEAD..HEAD")...
Is it clear? "git log HEAD~20..HEAD -- path" where path never changes
within the range would be !HAS_CHANGES, wouldn't it?
Perhaps "git log --exit-code --raw A..B -- path" should give the same exit
status as '! test -z "$(git rev-list A..B -- path)"'?
next prev parent reply other threads:[~2008-08-09 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 9:39 git diff/log --check exitcode and PAGER environment variable "Peter Valdemar Mørch (Lists)"
2008-08-08 9:44 ` Junio C Hamano
2008-08-08 10:04 ` "Peter Valdemar Mørch (Lists)"
2008-08-08 10:15 ` Re* " Junio C Hamano
2008-08-08 11:02 ` "Peter Valdemar Mørch (Lists)"
2008-08-08 11:23 ` Johannes Schindelin
2008-08-08 20:40 ` Junio C Hamano
2008-08-09 6:57 ` [PATCH] Teach git log --check to return an appropriate error code Peter Valdemar Mørch
2008-08-09 12:05 ` Johannes Schindelin
2008-08-09 19:29 ` Junio C Hamano
2008-08-10 17:05 ` "Peter Valdemar Mørch (Lists)"
2008-08-10 18:40 ` Junio C Hamano
2008-08-09 18:58 ` Junio C Hamano [this message]
2008-08-11 6:46 ` PATCH v2 0/2 Trying patch again Peter Valdemar Mørch
2008-08-11 6:46 ` [PATCH v2 1/2] Teach git log --check to return an appropriate exit code Peter Valdemar Mørch
2008-08-11 6:46 ` [PATCH v2 2/2] Teach git log --exit-code " Peter Valdemar Mørch
2008-08-08 13:17 ` git diff/log --check exitcode and PAGER environment variable Jeff King
2008-08-08 13:19 ` Jeff King
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=7vljz66mmt.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=4ux6as402@sneakemail.com \
--cc=git@vger.kernel.org \
/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).