From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2012, #10; Thu, 26)
Date: Fri, 27 Apr 2012 07:03:52 -0400 [thread overview]
Message-ID: <20120427110352.GA1828@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqlili6xfu.fsf@junio.mtv.corp.google.com>
On Thu, Apr 26, 2012 at 01:38:13PM -0700, Junio C Hamano wrote:
> * mm/include-userpath (2012-04-25) 2 commits
> (merged to 'next' on 2012-04-26 at c68e261)
> + fixup! config: expand tildes in include.path variable
> + config: expand tildes in include.path variable
>
> The new "include.path" directive in the configuration files learned
> to understand "~/path" and "~user/path".
Oops? Was this supposed to be squashed before merging to next?
-Peff
next prev parent reply other threads:[~2012-04-27 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 20:38 What's cooking in git.git (Apr 2012, #10; Thu, 26) Junio C Hamano
2012-04-27 11:03 ` Jeff King [this message]
2012-04-27 14:59 ` Junio C Hamano
2012-04-27 12:08 ` Tim Henigan
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=20120427110352.GA1828@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).