From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: k_f@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command.
Date: Tue, 6 Feb 2018 15:36:53 +0100 [thread overview]
Message-ID: <23161.48517.148291.638434@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <797b2499-a186-64b1-bc5a-f62f87047091@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
>>>>> On Tue, 6 Feb 2018, Kristian Fiskerstrand wrote:
>> Fixes: https://bugs.gentoo.org/446422
> Bug or Closes, Fixes would be referencing a commit-id c.f GLEP 66.
Updated, thanks for catching this.
> More generally though, should we start requiring more verbose commit
> messages for eclasses to make it easier to trace changes in our git
> repo directly without reaching out to bugs? At least including
> summaries of the respective bugs as a short description?
In the concrete example, the bug's summary is "bzr.eclass might need
to use bzr pull's --overwrite-tags flag" which is not much different
from the git commit message.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-02-06 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 13:57 [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command Ulrich Müller
2018-02-06 14:12 ` Kristian Fiskerstrand
2018-02-06 14:36 ` Ulrich Mueller [this message]
2018-02-06 14:40 ` eclass committ message verbosity (Was: Re: [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command.) Kristian Fiskerstrand
2018-02-06 17:07 ` [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command Alec Warner
2018-02-06 20:07 ` Michał Górny
2018-02-06 23:24 ` [gentoo-dev] [PATCH] bzr.eclass: Drop bzr_bootstrap and bzr_src_prepare Ulrich Müller
2018-02-07 7:34 ` Michał Górny
2018-02-07 13:18 ` Ulrich Mueller
2018-02-07 13:26 ` Michał Górny
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=23161.48517.148291.638434@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=k_f@gentoo.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