From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
John Keeping <john@keeping.me.uk>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH/RFC 0/2] fix some rev-parse options in non-repos
Date: Fri, 26 Feb 2016 18:25:08 -0500 [thread overview]
Message-ID: <20160226232507.GA9404@sigill.intra.peff.net> (raw)
Michael Haggerty noticed recently (off-list) that "git rev-parse
--local-env-vars" doesn't work outside of a git repository. This turns
out to be a regression in v1.8.5, due to a patch by John Keeping that
lifted some other restrictions on how the option could be used.
This fixes it by reverting John's patch, which puts the original
restrictions back in place. I won't repeat the lengthy discussion from
patch 2's commit message here, but the gist of it is that probably
nobody cares about those restrictions, it's more important to fix the
original regression, and it's probably too hard to make both work.
The only thing that gives me pause (and hence the RFC) is that it has
been over 2 years since the original regression. So it's entirely
possible somebody will consider _this_ fix a regression.
[1/2]: t1515: add tests for rev-parse out-of-repo helpers
[2/2]: Revert "rev-parse: remove restrictions on some options"
-Peff
next reply other threads:[~2016-02-26 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 23:25 Jeff King [this message]
2016-02-26 23:26 ` [PATCH 1/2] t1515: add tests for rev-parse out-of-repo helpers Jeff King
2016-02-26 23:29 ` [PATCH 2/2] Revert "rev-parse: remove restrictions on some options" Jeff King
2016-02-26 23:34 ` Jeff King
2016-02-26 23:44 ` Junio C Hamano
2016-02-27 3:22 ` Jeff King
2016-02-29 11:01 ` Jeff King
2016-02-29 17:32 ` Junio C Hamano
2016-02-29 21:29 ` Jeff King
2016-02-27 12:25 ` John Keeping
2016-02-29 11:11 ` Jeff King
2016-02-28 0:53 ` Eric Sunshine
2016-02-29 11:12 ` 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=20160226232507.GA9404@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=mhagger@alum.mit.edu \
/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).