Dnia 2015-08-10, o godz. 02:16:01 Andrew Savchenko <birc...@gentoo.org> 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, > > > > - 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. Not really. You are closer to the threshold when you are too lazy to type it and you just copy-paste it. > > > 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. How is: Bug: 123451, 453445, 344334, 343444 more readable than: Bug: https://bugs.gentoo.org/123451 Bug: https://bugs.gentoo.org/453445 Bug: https://bugs.gentoo.org/344334 Bug: https://bugs.gentoo.org/343444 Readability is a matter of formatting, not contents. > > > 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? As far as I'm aware, URLs are supported much more widely than Gentoo-specific bug numbers. They are uniform and unique by definition. The tools using bug numbers can be easily expanded to extract them from URLs. I don't really see forking cgit to support Gentoo bug numbers, or asking github to provide special rules for our commits. > > > 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. Which reminds me of the metadata.xml discussion. These days we have transparent compression which handles redundant data much better than explicit obfuscation, and with much less harm. -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgp4YORhnUYTk.pgp
Description: OpenPGP digital signature
