From: "Michał Górny" <mgorny@gentoo.org>
To: 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, 06 Feb 2018 21:07:29 +0100 [thread overview]
Message-ID: <1517947649.1390.0.camel@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr9GnT_8-AkWP3DSGA3H5SzEzMhnKjFB0kkyjfwAZL2QUQ@mail.gmail.com>
W dniu wto, 06.02.2018 o godzinie 09∶07 -0800, użytkownik Alec Warner
napisał:
> 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.
>
That's very nice of you. I do really enjoy when I have a log of like 30
different commits that might be relevant and whose descriptions boil
down to 'go see 30 bugs, and hope you won't have to read all comments'.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2018-02-06 20: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 ` [gentoo-dev] [PATCH] bzr.eclass: Add --overwrite-tags option to pull command Alec Warner
2018-02-06 20:07 ` Michał Górny [this message]
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=1517947649.1390.0.camel@gentoo.org \
--to=mgorny@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