>
> Someone end the bikeshed train please.
Seconded.
On 08/11/2015 10:12 AM, Michał Górny wrote:
> Dnia 2015-08-11, o godz. 09:56:55
> Dmitry Yu Okunev napisał(a):
>> On 08/11/2015 12:06 AM, Michał Górny wrote:
3. Too many text, hard to read. Some bugs may refer to a dozen of
URLs.
>>>
>>> And how is a dozen numbers bette
Dnia 2015-08-11, o godz. 09:56:55
Dmitry Yu Okunev napisał(a):
> Hello.
>
> I'm not a gentoo-dev, so sorry if I shouldn't express my thoughts with
> my lame English here. Please tell me if it's so.
>
> On 08/11/2015 12:06 AM, Michał Górny wrote:
> >> 3. Too many text, hard to read. Some bug
Hello.
I'm not a gentoo-dev, so sorry if I shouldn't express my thoughts with
my lame English here. Please tell me if it's so.
On 08/11/2015 12:06 AM, Michał Górny wrote:
>> 3. Too many text, hard to read. Some bugs may refer to a dozen of
>> URLs.
>
> And how is a dozen numbers b
Dnia 2015-08-10, o godz. 23:43:29
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 15:11:02 +0200 Michał Górny wrote:
> > > > > 2. Bug number can be easily typed, URL has to be copied or
> > > > > generated by some tool.
> > > >
> > > > So, please remind me, how many times the 'easy typing' go
On Mon, 10 Aug 2015 15:11:02 +0200 Michał Górny wrote:
> > > > 2. Bug number can be easily typed, URL has to be copied or
> > > > generated by some tool.
> > >
> > > So, please remind me, how many times the 'easy typing' got the bug
> > > number wrong? This is not a real argument, just another of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michał Górny schrieb:
>> I prefer the
>>
>> Bugzilla: https://bugs.gentoo.org/show_bug.cgi?id=333531
>>
>> format even though not all bug trackers are running Bugzilla. "Bug: "
>> works fine with me too, and we could make
>> "https://bugs.gentoo.org
On 08/10/2015 03:19 PM, Michał Górny wrote:
>
> Thanks, this is exactly what I wanted.
>
> "Fixes", "References", "Bug" are all good. "Bugzilla" goes against your
> proposal diverging keyword depending on bug tracker software.
>
Afaik "Fixes: " is for referencing commits, not bug reports.
And
Dnia 2015-08-10, o godz. 11:45:33
Chí-Thanh Christopher Nguyễn napisał(a):
> Ulrich Mueller schrieb:
> >> This is not a matter of going l33t, this is a matter of getting rid of
> >> redundant and pretty much useless data all the same through almost all
> >> commit messages.
> >
> > +1
> >
> > "
Dnia 2015-08-10, o godz. 02:16:01
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 00:40:44 +0200 Michał Górny wrote:
> > > > Which is terribly redundant. Just put the whole bug URL. Advantages:
> > > >
> > > > - keeps the bug namespaced to bugs.gentoo.org,
> > > > - has the bug no inside,
> >
> On Mon, 10 Aug 2015, Chí-Thanh Christopher Nguyễn wrote:
> I prefer the
> Bugzilla: https://bugs.gentoo.org/show_bug.cgi?id=333531
> format even though not all bug trackers are running Bugzilla.
> "Bug: " works fine with me too,
There are bug trackers other than bugzilla, for example
debb
Ulrich Mueller schrieb:
>> This is not a matter of going l33t, this is a matter of getting rid of
>> redundant and pretty much useless data all the same through almost all
>> commit messages.
>
> +1
>
> "Gentoo-Bug: 123456" or even "Bug: 123456" is enough to uniquely
> identify a bug. Also it is
On Sun, 9 Aug 2015 17:02:27 -0700 Daniel Campbell (zlg) wrote:
> I don't know about you guys, but I have a "smart bookmark" in Firefox
> where I type "bgo xx" and it'll take me to the relevant bug. It'd
> be trivial to set that up as a bash alias, too. There are tons of ways
> to get to a bug;
On 08/10/2015 02:51 AM, Ulrich Mueller wrote:
>> On Mon, 10 Aug 2015, Andrew Savchenko wrote:
>
>> This is not a matter of going l33t, this is a matter of getting rid
>> of redundant and pretty much useless data all the same through
>> almost all commit messages.
>
> +1
>
> "Gentoo-Bug: 1234
> On Mon, 10 Aug 2015, Andrew Savchenko wrote:
> This is not a matter of going l33t, this is a matter of getting rid
> of redundant and pretty much useless data all the same through
> almost all commit messages.
+1
"Gentoo-Bug: 123456" or even "Bug: 123456" is enough to uniquely
identify a b
On Sun, 2015-08-09 at 17:30 +0200, hasufell wrote:
> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
> > On Sun, 09 Aug 2015, Sven Vermeulen wrote:
> >
> > I'd just go with "Gentoo-Bug". The X- is pointless since it was
> > for eXtending Email-Headers. And what we do is only linked in
> > style.
>
On 10 August 2015 at 11:46, hasufell wrote:
> As I see it, a lot of people already stuff the bug number into the
> summary and I can't really say anything against that. It gives a nice
> overview when you look at it:
> https://gitweb.gentoo.org/repo/gentoo.git/log/
>
> Given that fact, I am not su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/09/2015 04:46 PM, hasufell wrote:
> As I see it, a lot of people already stuff the bug number into the
> summary and I can't really say anything against that. It gives a
> nice overview when you look at it:
> https://gitweb.gentoo.org/repo/ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/09/2015 02:11 PM, Michał Górny wrote:
> Dnia 2015-08-09, o godz. 23:01:32 hasufell
> napisał(a):
>
>> On 08/09/2015 09:56 PM, Michał Górny wrote:
>>> Dnia 2015-08-09, o godz. 16:09:29 hasufell
>>> napisał(a):
>>>
On 08/09/2015 03:58 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/09/2015 11:49 AM, Davide Pesavento wrote:
> On Sun, Aug 9, 2015 at 8:43 AM, Mike Gilbert
> wrote:
>> On Sun, Aug 9, 2015 at 11:30 AM, hasufell
>> wrote:
>>> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
Hi!
On Sun, 09 Aug 20
As I see it, a lot of people already stuff the bug number into the
summary and I can't really say anything against that. It gives a nice
overview when you look at it:
https://gitweb.gentoo.org/repo/gentoo.git/log/
Given that fact, I am not sure we can convince people to repeat the bug
number in th
On Mon, 10 Aug 2015 00:40:44 +0200 Michał Górny wrote:
> > > Which is terribly redundant. Just put the whole bug URL. Advantages:
> > >
> > > - keeps the bug namespaced to bugs.gentoo.org,
> > > - has the bug no inside,
> > > - is convenient -- you can click it instead of copy-pasting the no.
> >
Dnia 2015-08-10, o godz. 00:44:09
Andrew Savchenko napisał(a):
> On Sun, 9 Aug 2015 21:56:05 +0200 Michał Górny wrote:
> > Dnia 2015-08-09, o godz. 16:09:29
> > hasufell napisał(a):
> >
> > > On 08/09/2015 03:58 PM, Michael Weber wrote:
> > > > commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24
On Sun, 9 Aug 2015 21:56:05 +0200 Michał Górny wrote:
> Dnia 2015-08-09, o godz. 16:09:29
> hasufell napisał(a):
>
> > On 08/09/2015 03:58 PM, Michael Weber wrote:
> > > commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
> > > Author: Michael Weber gentoo org>
> > > AuthorDate: Sun Aug 9
On Sun, Aug 9, 2015 at 5:11 PM, Michał Górny wrote:
> X-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=557022
How about just:
Bug-URL: xxx
or Bug: xxx
X- is not recommended as a prefix for the various reasons already
well-stated by the IETF in the previously-linked RFC.
--
Rich
Dnia 2015-08-09, o godz. 23:01:32
hasufell napisał(a):
> On 08/09/2015 09:56 PM, Michał Górny wrote:
> > Dnia 2015-08-09, o godz. 16:09:29
> > hasufell napisał(a):
> >
> >> On 08/09/2015 03:58 PM, Michael Weber wrote:
> >>> commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
> >>> Author:
On 08/09/2015 09:56 PM, Michał Górny wrote:
> Dnia 2015-08-09, o godz. 16:09:29
> hasufell napisał(a):
>
>> On 08/09/2015 03:58 PM, Michael Weber wrote:
>>> commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
>>> Author: Michael Weber gentoo org>
>>> AuthorDate: Sun Aug 9 13:58:26 2015 +0
Dnia 2015-08-09, o godz. 16:09:29
hasufell napisał(a):
> On 08/09/2015 03:58 PM, Michael Weber wrote:
> > commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
> > Author: Michael Weber gentoo org>
> > AuthorDate: Sun Aug 9 13:58:26 2015 +
> > Commit: Michael Weber gentoo org>
> >
On Sun, Aug 9, 2015 at 8:43 AM, Mike Gilbert wrote:
> On Sun, Aug 9, 2015 at 11:30 AM, hasufell wrote:
>> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
>>> Hi!
>>>
>>> On Sun, 09 Aug 2015, Sven Vermeulen wrote:
>>>
On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
>> I t
On Sun, Aug 9, 2015 at 11:30 AM, hasufell wrote:
> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
>> Hi!
>>
>> On Sun, 09 Aug 2015, Sven Vermeulen wrote:
>>
>>> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
> I think "X-Gentoo-Bug: 557022" also makes the job easier for tool
On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
> Hi!
>
> On Sun, 09 Aug 2015, Sven Vermeulen wrote:
>
>> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
parse commit messages.
>>>
>>> I don't. Jus
Hi!
On Sun, 09 Aug 2015, Sven Vermeulen wrote:
> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
> > > I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
> > > parse commit messages.
> >
> > I don't. Just the "bug " prefix should be fine for almost all
> >
On 08/09/2015 05:03 PM, Sven Vermeulen wrote:
> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
>>> I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
>>> parse commit messages.
>>
>> I don't. Just the "bug " prefix should be fine for almost all
>> purposes, ev
On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
> > I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
> > parse commit messages.
>
> I don't. Just the "bug " prefix should be fine for almost all
> purposes, even for tools.
I'm pretty sure the majority of dev
On 08/09/2015 10:43 AM, Dirkjan Ochtman wrote:
> On Sun, Aug 9, 2015 at 4:38 PM, hasufell wrote:
>>> I don't really see why it has to be so verbose. Can we just make it
>>> "bug 557022", or even #557022? That would also make it fit better if
>>> you have a single-line commit message only.
>>
>> I
On 08/09/2015 04:43 PM, Dirkjan Ochtman wrote:
> On Sun, Aug 9, 2015 at 4:38 PM, hasufell wrote:
>>> I don't really see why it has to be so verbose. Can we just make it
>>> "bug 557022", or even #557022? That would also make it fit better if
>>> you have a single-line commit message only.
>>
>> I
On Sun, Aug 9, 2015 at 4:38 PM, hasufell wrote:
>> I don't really see why it has to be so verbose. Can we just make it
>> "bug 557022", or even #557022? That would also make it fit better if
>> you have a single-line commit message only.
>
> I think "X-Gentoo-Bug: 557022" also makes the job easier
On 08/09/2015 04:26 PM, Dirkjan Ochtman wrote:
> On Sun, Aug 9, 2015 at 4:09 PM, hasufell wrote:
>> I was wondering if we should set a standard for referencing bug reports.
>> The portage team already does something like that:
>> https://github.com/gentoo/portage/commit/b7149002bf23889f280c502afe6
On Sun, Aug 9, 2015 at 4:09 PM, hasufell wrote:
> I was wondering if we should set a standard for referencing bug reports.
> The portage team already does something like that:
> https://github.com/gentoo/portage/commit/b7149002bf23889f280c502afe6ceda0b1345ca3
>
> Following that, the commit could h
On 9 August 2015 at 15:09, hasufell wrote:
> On 08/09/2015 03:58 PM, Michael Weber wrote:
> > commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
> > Author: Michael Weber gentoo org>
> > AuthorDate: Sun Aug 9 13:58:26 2015 +
> > Commit: Michael Weber gentoo org>
> > CommitDate:
On 08/09/2015 03:58 PM, Michael Weber wrote:
> commit: 40b3fd64ec9c5d6d94f0f0897740bc77622c24a1
> Author: Michael Weber gentoo org>
> AuthorDate: Sun Aug 9 13:58:26 2015 +
> Commit: Michael Weber gentoo org>
> CommitDate: Sun Aug 9 13:58:26 2015 +
> URL:https://git
41 matches
Mail list logo
