From: Ken Dreyer <kdreyer@redhat.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: proposal to stop using "backport: " in commit logs
Date: Mon, 13 Apr 2015 10:48:09 -0600 [thread overview]
Message-ID: <552BF349.50909@redhat.com> (raw)
A while ago this came up in #ceph-devel and I wanted to bring it to a
wider audience.
Should we stop the convention of adding the "backport: " tags in Git?
Loic brought up the point that this data is essentially immutable after
we merge it, and it's better to point at a Redmine tracker where we can
alter the "backport" field.
This makes it easier to adjust the "backport" data after the code's been
merged to master. It also makes it easier for whoever is corralling the
backport efforts, because the person only have one place to look
(Redmine) instead of two (Redmine + git commit logs).
For what it's worth I agree with Loic on this.
Any objections?
- Ken
next reply other threads:[~2015-04-13 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:48 Ken Dreyer [this message]
2015-04-13 16:49 ` proposal to stop using "backport: " in commit logs Sage Weil
2015-04-13 17:04 ` Gregory Farnum
2015-04-13 17:28 ` Loic Dachary
2015-04-13 18:53 ` Gregory Farnum
2015-04-13 20:04 ` Loic Dachary
2015-04-13 23:59 ` Joao Eduardo Luis
2015-04-13 17:04 ` Loic Dachary
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=552BF349.50909@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.