Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: ding@gnus.org
Subject: Re: Git support question part XXIV
Date: Thu, 02 Feb 2012 11:38:57 +0100	[thread overview]
Message-ID: <m2k445seny.fsf@igel.home> (raw)
In-Reply-To: <8762fp4jiq.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 02 Feb 2012 11:27:57 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> It seems like the ChangeLog "diff" gets longer and longer and longer the
> more I merge.  But the bogus lines start with " +" instead of "+", so
> it's not really a diff, either.  So I'm wondering what it's doing, and
> whether I'm doing anything wrong.

See git-diff(1), section COMBINED DIFF FORMAT for the description of the
format.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2012-02-02 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 10:27 Lars Ingebrigtsen
2012-02-02 10:38 ` Andreas Schwab [this message]
2012-02-02 10:41   ` Lars Ingebrigtsen
2012-02-02 10:55     ` Andreas Schwab
2012-02-02 12:40       ` Steinar Bang
2012-02-02 12:43         ` Lars Ingebrigtsen

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=m2k445seny.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=ding@gnus.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).