Jeff King writes:
> On Tue, Jan 08, 2013 at 03:36:09PM -0800, Junio C Hamano wrote:
>
>> You could introduce a new configuration variable "am.scissors" and
>> personally turn it on, though. Setting that variable *does* count
>> as the user explicitly asking for it.
>
> I think we have mailinfo.s
On Tue, Jan 08, 2013 at 03:36:09PM -0800, Junio C Hamano wrote:
> You could introduce a new configuration variable "am.scissors" and
> personally turn it on, though. Setting that variable *does* count
> as the user explicitly asking for it.
I think we have mailinfo.scissors already.
> > I often
Phillip Susi writes:
> On 01/08/2013 05:42 PM, Junio C Hamano wrote:
>> It is very easy to miss misidentification of scissors line; as a
>> dangerous, potentially information losing option, I do not think
>> it should be on by default.
>
> I suppose if it only requires one instance of >8 or <8 a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2013 05:42 PM, Junio C Hamano wrote:
> It is very easy to miss misidentification of scissors line; as a
> dangerous, potentially information losing option, I do not think
> it should be on by default.
I suppose if it only requires one instan
Phillip Susi writes:
> I was wondering why am's scissors option is not enabled by default.
It is very easy to miss misidentification of scissors line; as a
dangerous, potentially information losing option, I do not think it
should be on by default.
Another reason (and this is the original one)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was wondering why am's scissors option is not enabled by default.
It seems a very handy feature, but I'm reluctant to use it when
sending patches because the recipient has to notice the scissors and
remember to pass --scissors to git am.
Could this
6 matches
Mail list logo