From: Thomas Rast <trast@student.ethz.ch>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, <git@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.10
Date: Tue, 10 Apr 2012 21:11:12 +0200 [thread overview]
Message-ID: <878vi3mmgf.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <m3398bbf7y.fsf@localhost.localdomain> (Jakub Narebski's message of "Tue, 10 Apr 2012 11:43:46 -0700 (PDT)")
Jakub Narebski <jnareb@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Git v1.7.10 Release Notes
>> =========================
>>
>> Compatibility Notes
>> -------------------
> [...]
>> * The "--binary/-b" options to "git am" have been a no-op for quite a
>> while and were deprecated in mid 2008 (v1.6.0). When you give these
>> options to "git am", it will now warn and ask you not to use them.
> [...]
>> Updates since v1.7.9
>> --------------------
> [...]
>> * "git am" learned to pass "-b" option to underlying "git mailinfo", so
>> that a bracketed string other than "PATCH" at the beginning can be kept.
>
> So how it is in 1.7.10? Is "git am -b ..." a no-op, now showing
> deprecation notice, or does it pass "-b" to "git mailinfo" to limit
> stripping of bracketed strings to those containing the word "PATCH"?
The option to pass down -b from git-am is called --keep-non-patch. The
deprecation of -b is meant to let us call it -b for convenience in a
later release.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2012-04-10 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 20:48 [ANNOUNCE] Git 1.7.10 Junio C Hamano
2012-04-10 18:43 ` Jakub Narebski
2012-04-10 19:11 ` Thomas Rast [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=878vi3mmgf.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=linux-kernel@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).