From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Josh Sharpe <josh.m.sharpe@gmail.com>,
git@vger.kernel.org
Subject: Re: feature request - have git honor nested .gitconfig files
Date: Sun, 24 Mar 2013 00:14:45 -0700 [thread overview]
Message-ID: <7vehf52rru.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130323080341.GA29768@sigill.intra.peff.net> (Jeff King's message of "Sat, 23 Mar 2013 04:03:41 -0400")
Jeff King <peff@peff.net> writes:
> Yeah, I'm not planning to work on this, but I'd be happy to review
> patches if somebody else wants to.
I am not planning to work on this, and honestly speaking I would not
be very happy to see any patch in this area.
next prev parent reply other threads:[~2013-03-24 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 16:50 feature request - have git honor nested .gitconfig files Josh Sharpe
2013-03-22 18:22 ` Jonathan Nieder
2013-03-22 18:33 ` Jeff King
2013-03-23 0:06 ` Jonathan Nieder
2013-03-23 8:03 ` Jeff King
2013-03-24 7:14 ` Junio C Hamano [this message]
2013-03-23 6:15 ` Thomas Rast
2013-03-23 8:06 ` 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=7vehf52rru.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=josh.m.sharpe@gmail.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).