git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincenzo di Cicco <enzodicicco@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	Jeff King <peff@peff.net>, Git List <git@vger.kernel.org>
Subject: Re: Reference to a commit inside a commit message
Date: Wed, 30 Apr 2014 20:29:38 +0200	[thread overview]
Message-ID: <CAKOJyXduybjMEvkw6e2LijTa553mEPqe2_ELfVy_QZ5kc=RrRg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1q2zdJZVkJVsNtGfN35LFmuK5txd91nTak5kGmvvKdWA@mail.gmail.com>

> You should use the latest version of the patch series (v11), because the
> blank line is now automatically added.

Yes interpret-trailers add the blank line, but when call `git commit
-m "$MSG" -e` it isn't displayed.
I think this happens due to the default value of 'cleanup' option of
git-commit that is 'strip' (in my case) when the message is edited.
I can't use neither 'verbatim' nor 'whitespace' otherwise all the
comments will be displayed.

> And using ':' instead of '=' after "see-also" would be more standard.

Thanks I've updated my script and now I'm using the latest interpret-trailers.

NaN

      parent reply	other threads:[~2014-04-30 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 18:35 Reference to a commit inside a commit message enzodicicco
2014-04-28 19:55 ` Jonathan Nieder
2014-04-28 20:43   ` Vincenzo di Cicco
2014-04-29  3:41 ` Jeff King
2014-04-29  7:57   ` Felipe Contreras
2014-04-29 23:23     ` Vincenzo di Cicco
     [not found]       ` <CAP8UFD1q2zdJZVkJVsNtGfN35LFmuK5txd91nTak5kGmvvKdWA@mail.gmail.com>
2014-04-30 18:29         ` Vincenzo di Cicco [this message]

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='CAKOJyXduybjMEvkw6e2LijTa553mEPqe2_ELfVy_QZ5kc=RrRg@mail.gmail.com' \
    --to=enzodicicco@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).