Re: [PATCH] git-contacts: do not fail parsing of good diffs

On 19 February 2014 00:14, Junio C Hamano wrote: [...] > The patch was whitespace damaged, by the way. It was easy to hand > tweak so there is no need to resend this particular patch, but if > you are planning to send more patches, please check your MUA and > tell it not to. Suits me right for d

[PATCH] git-contacts: do not fail parsing of good diffs

acts. Signed-off-by: Lars Gullik Bjønnes --- contrib/contacts/git-contacts | 2 -- 1 file changed, 2 deletions(-) diff --git a/contrib/contacts/git-contacts b/contrib/contacts/git-contacts index 428cc1a..dbe2abf 100755 --- a/contrib/contacts/git-contacts +++ b/contrib/contacts/git-contacts @

Re: [PATCH 01/11] Call it "Git User Manual" and remove reference to very old Git version

Junio C Hamano writes: | Thomas Ackermann writes: > >> Reviewed-by: Jonathan Nieder >> Signed-off-by: Thomas Ackermann >> --- > | I tend to agree with Jonathan that this should be "User's Manual". Not going into which one might be more correct, but a quick google search for "User's Manual" a

Re: Wrap commit messages on `git commit -m`

Ramkumar Ramachandra writes: | Hi, > | Some of my colleagues are lazy to fire up an editor and write proper | commit messages- they often write one-liners using `git commit -m`. | However, that line turns out to be longer than 72 characters, and the | resulting `git log` output is ugly. So, I wa