From: Tom Wijsman <TomWij@gentoo.org>
To: SebastianLuther@gmx.de
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Document bugzilla workflow
Date: Wed, 15 Jan 2014 23:49:16 +0100 [thread overview]
Message-ID: <20140115234916.0fd095e6@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52D6F30E.9070402@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Wed, 15 Jan 2014 21:43:58 +0100
Sebastian Luther <SebastianLuther@gmx.de> wrote:
> 1) If you fix something that has a bug, you should refer to that in
> the git commit message.
Yes, this might need to go into the commit policy.
> What I meant was to allow people to test different styles and hope
> that the one that works best will be adopted by everyone at some
> point. Once that happens you can document that style.
Some styles only work properly if everyone uses the style; otherwise,
there's no point to doing the style because nobody else follows.
> Yes, maybe. One then needs to see if that is a problem and if it is
> then force everyone to use one style.
It is already raised as a problem in this thread.
> > It's already making people unhappy right now; because as it is
> > documented now, it is turned from the meaningful experience that
> > the previous Portage team had before to something that is
> > meaningless. It is a regression in checking the list of bugs that
> > block the tracker, as the states of the bugs no longer have a value
> > as it is documented now.
> >
> Previously the bug state was not used at all. There is no regression.
https://bugs.gentoo.org/show_bug.cgi?id=470992#c10
https://bugs.gentoo.org/show_bug.cgi?id=476738#c1
https://bugs.gentoo.org/show_bug.cgi?id=481366#c3
https://bugs.gentoo.org/show_bug.cgi?id=482650#c1
https://bugs.gentoo.org/show_bug.cgi?id=483628#c2
https://bugs.gentoo.org/show_bug.cgi?id=485226#c1
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2014-01-15 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:25 [gentoo-portage-dev] [PATCH] Document bugzilla workflow SebastianLuther
2014-01-15 3:11 ` Tom Wijsman
2014-01-15 6:29 ` Sebastian Luther
2014-01-15 16:20 ` Tom Wijsman
2014-01-15 17:29 ` Sebastian Luther
2014-01-15 18:41 ` Tom Wijsman
2014-01-15 20:43 ` Sebastian Luther
2014-01-15 22:49 ` Tom Wijsman [this message]
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=20140115234916.0fd095e6@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=SebastianLuther@gmx.de \
--cc=gentoo-portage-dev@lists.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