git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Bertrand <xda@abalgo.com>
To: arnaud.bertrand@abalgo.com
Cc: git@vger.kernel.org, gitster@pobox.com, xda@abalgo.com
Subject: [RFC PATCH 0/2 v2] *** Add branchname in commit when core.branchnameincommit is set ***
Date: Mon, 30 Dec 2019 17:32:54 +0100	[thread overview]
Message-ID: <20191230163256.14749-1-xda@abalgo.com> (raw)
In-Reply-To: <20191229222633.23815-1-arnaud.bertrand@abalgo.com>

To avoid any change in the current git behaviour by default, I've added
a configuration variable that allow to activate the feature for those
who want to see the branchname in commit. 
By default, this feature is disabled

Arnaud Bertrand (2):
  Add branchname in commit header
  Add the configuration parameter core.branchnameincommit

 Documentation/pretty-formats.txt |  1 +
 cache.h                          |  1 +
 commit.c                         | 21 +++++++++++++++++++++
 config.c                         |  5 +++++
 environment.c                    |  1 +
 pretty.c                         | 15 +++++++++++++++
 6 files changed, 44 insertions(+)

-- 
2.25.0.rc0.7.g17b02bf28a


  parent reply	other threads:[~2019-12-30 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 22:26 [RFC PATCH 0/1] *** Add branchname in commit header *** Arnaud Bertrand
2019-12-29 22:26 ` [RFC PATCH 1/1] Add branchname in commit header Arnaud Bertrand
2019-12-30  2:32 ` [RFC PATCH 0/1] *** Add branchname in commit header *** brian m. carlson
2019-12-30 10:33   ` Arnaud Bertrand
2019-12-30 16:32 ` Arnaud Bertrand [this message]
2019-12-30 16:32   ` [RFC PATCH 1/2 v2] Add branchname in commit header Arnaud Bertrand
2019-12-30 16:32   ` [RFC PATCH 2/2 v2] Add the configuration parameter core.branchnameincommit Arnaud Bertrand

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=20191230163256.14749-1-xda@abalgo.com \
    --to=xda@abalgo.com \
    --cc=arnaud.bertrand@abalgo.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).