lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 10 Apr 2012 21:11:12 +0200
From:	Thomas Rast <trast@...dent.ethz.ch>
To:	Jakub Narebski <jnareb@...il.com>
CC:	Junio C Hamano <gitster@...ox.com>, <git@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.10

Jakub Narebski <jnareb@...il.com> writes:

> Junio C Hamano <gitster@...ox.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@...f,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ