From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: "Ulrich Müller" <ulm@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command.
Date: Tue, 6 Feb 2018 09:07:28 -0800 [thread overview]
Message-ID: <CAAr7Pr9GnT_8-AkWP3DSGA3H5SzEzMhnKjFB0kkyjfwAZL2QUQ@mail.gmail.com> (raw)
In-Reply-To: <797b2499-a186-64b1-bc5a-f62f87047091@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Tue, Feb 6, 2018 at 6:12 AM, Kristian Fiskerstrand <k_f@gentoo.org>
wrote:
> On 02/06/2018 02:57 PM, Ulrich Müller wrote:
> > Fixes: https://bugs.gentoo.org/446422
>
> Bug or Closes, Fixes would be referencing a commit-id c.f GLEP 66.
>
> 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?
>
Nope, people can go read the bug.
-A
>
> --
> Kristian Fiskerstrand
> OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
>
>
[-- Attachment #2: Type: text/html, Size: 1425 bytes --]
next prev parent reply other threads:[~2018-02-06 17:07 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
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 ` Alec Warner [this message]
2018-02-06 20:07 ` [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command 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=CAAr7Pr9GnT_8-AkWP3DSGA3H5SzEzMhnKjFB0kkyjfwAZL2QUQ@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@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