From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/)
Date: Mon, 10 Aug 2015 02:16:01 +0300 [thread overview]
Message-ID: <20150810021601.cdcae7226373ecd0d284086a@gentoo.org> (raw)
In-Reply-To: <20150810004044.76dda6e6@pomiot>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
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.
> >
> > 1. URL may change in future, bug number — unlikely.
>
> If the URL changes, we need to provide backwards compatibility. Too
> many resources already depend on that.
>
> > 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 Gentoo's
> 'I'm too lazy to do things right'.
URLs are longer, so probability of error during typing increases
compared to raw numbers.
> > 3. Too many text, hard to read. Some bugs may refer to a dozen of
> > URLs.
>
> And how is a dozen numbers better?
Less text, more readable.
> > 4. It is easier to copy a number, than selecting and copying whole
> > string. Not all terminals support running browser on URL click.
>
> So we should optimize for a corner case?
What is a corner case? Why not defining "clicking on the link in
the git log" as a corner case?
> > 5. Clicking is less convenient than typing "bugs search $number" —
> > user have to move hands from a keyboard to a mouse — a terrible
> > waste of time, at least in my case with my typing speed.
>
> You can type the number you see at the end of the URL. If you really
> want to go l33t, that shouldn't a problem for you.
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.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-09 23:16 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439128706.40b3fd64ec9c5d6d94f0f0897740bc77622c24a1.xmw@gentoo>
2015-08-09 14:09 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) hasufell
2015-08-09 14:18 ` Ian Whyman
2015-08-09 14:26 ` Dirkjan Ochtman
2015-08-09 14:38 ` hasufell
2015-08-09 14:43 ` Dirkjan Ochtman
2015-08-09 14:47 ` hasufell
2015-08-09 14:54 ` Michael Orlitzky
2015-08-09 15:03 ` Sven Vermeulen
2015-08-09 15:06 ` hasufell
2015-08-09 15:19 ` Tobias Klausmann
2015-08-09 15:30 ` hasufell
2015-08-09 15:43 ` Mike Gilbert
2015-08-09 18:49 ` Davide Pesavento
2015-08-09 23:58 ` Daniel Campbell (zlg)
2015-08-10 0:25 ` Alexandre Rostovtsev
2015-08-09 19:56 ` Michał Górny
2015-08-09 21:01 ` hasufell
2015-08-09 21:11 ` Michał Górny
2015-08-09 21:30 ` Rich Freeman
2015-08-10 0:02 ` Daniel Campbell (zlg)
2015-08-10 7:31 ` Andrew Savchenko
2015-08-09 21:44 ` Andrew Savchenko
2015-08-09 22:40 ` Michał Górny
2015-08-09 23:16 ` Andrew Savchenko [this message]
2015-08-09 23:46 ` hasufell
2015-08-10 0:05 ` Daniel Campbell (zlg)
2015-08-10 0:10 ` Kent Fredric
2015-08-10 0:51 ` [gentoo-dev] Referencing bug reports in git Ulrich Mueller
2015-08-10 1:02 ` hasufell
2015-08-10 4:29 ` [gentoo-dev] " Ryan Hill
2015-08-10 12:25 ` Duncan
2015-08-10 22:57 ` Gordon Pettey
2015-08-11 1:03 ` Duncan
2015-08-11 0:17 ` Ryan Hill
2015-08-11 1:25 ` Duncan
2015-08-11 8:57 ` Tobias Klausmann
2015-08-11 9:12 ` Kent Fredric
2015-08-11 11:49 ` Rich Freeman
2015-08-11 11:58 ` hasufell
2015-08-12 7:20 ` [gentoo-dev] Bisecting Was: " Duncan
2015-08-12 7:38 ` Jason Zaman
2015-08-12 8:42 ` [gentoo-dev] " Duncan
2015-08-11 14:28 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Ian Stakenvicius
2015-08-11 14:35 ` Kent Fredric
2015-08-11 15:27 ` [gentoo-dev] Summary line Ian Stakenvicius
2015-08-31 14:53 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Alec Warner
2015-08-31 17:33 ` Rich Freeman
2015-08-31 18:16 ` [gentoo-dev] Summary line Michael Orlitzky
2015-08-11 14:36 ` hasufell
2015-08-11 14:39 ` Mikle Kolyada
2015-08-10 9:45 ` [gentoo-dev] Referencing bug reports in git Chí-Thanh Christopher Nguyễn
2015-08-10 10:16 ` Ulrich Mueller
2015-08-10 13:19 ` Michał Górny
2015-08-10 14:42 ` hasufell
2015-08-10 18:44 ` Chí-Thanh Christopher Nguyễn
2015-08-10 13:11 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) Michał Górny
2015-08-10 20:43 ` Andrew Savchenko
2015-08-10 21:06 ` Michał Górny
2015-08-11 6:56 ` Dmitry Yu Okunev
2015-08-11 7:12 ` Michał Górny
2015-08-11 8:34 ` Dmitry Yu Okunev
2015-08-11 0:52 ` [gentoo-dev] " Ryan Hill
2015-08-10 0:08 ` Ryan Hill
2015-08-12 10:40 ` [gentoo-dev] Re: Referencing bug reports in git hasufell
2015-08-12 15:59 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:03 ` Michał Górny
2015-08-12 16:25 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:34 ` Michał Górny
2015-08-12 16:39 ` Ian Stakenvicius
2015-08-13 5:48 ` Ryan Hill
2015-08-13 11:19 ` Ben de Groot
2015-08-13 12:13 ` Rich Freeman
2015-08-14 13:37 ` Aaron W. Swenson
2015-08-18 6:03 ` Ryan Hill
2015-08-14 20:04 ` Andrew Savchenko
2015-08-14 20:17 ` Matthias Maier
2015-08-15 7:17 ` Daniel Campbell (zlg)
2015-08-12 16:15 ` hasufell
2015-08-12 17:38 ` Matt Turner
2015-08-12 17:48 ` Dmitry Yu Okunev
2015-08-12 17:54 ` hasufell
2015-08-13 2:30 ` [gentoo-dev] " Steev Klimaszewski
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=20150810021601.cdcae7226373ecd0d284086a@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-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