Re: git log -p unexpected behaviour - security risk?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 30, 2013, 16:37 UTC
- Message-ID
- <7va9ogezzx.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CAEBDL5VspccUmkkYBf17soGTyT3sinjnnNzRB_kytnOr3OBVQw@mail.gmail.com>
John Szakmeister <john@szakmeister.net> writes:
Show 9 quoted lines
>> When I added -c/--cc, I contemplated making -p imply --cc, but >> decided against it primarily because it is a change in traditional >> behaviour, and it is easy for users to say --cc instead of -p from >> the command line. > > FWIW, security aside, I would've like to have seen that. I find it > confusing that merge commits that introduce code don't have a diff > shown when using -p. And I find it hard to remember --cc. BTW, > what's the mnemonic for it? -p => patch, --cc => ?
Compact combined.
By the way, these options are _not_ about "showing merge commits that introduce code", and they do not help your kind of "security". As I repeatedly said, you would need "-p -m" for that.