1 |
On Sun, 26 Feb 2017 19:59:19 +0000 Robin H. Johnson wrote: |
2 |
|
3 |
>On Sat, Feb 25, 2017 at 03:05:09PM +0100, Ulrich Mueller wrote: |
4 |
>> As the council has decided in its 2014-10-14 meeting (and confirmed |
5 |
>> again in the 2016-11-13 meeting), CVS headers should be removed after |
6 |
>> the migration to Git. |
7 |
>The 2014-10-14 meeting did NOT specify what CVS headers were in |
8 |
>question, and it was later decided that this was $Header$, not $Id$. |
9 |
> |
10 |
>> Until recently, this was blocked by repoman still checking for the |
11 |
>> $Id$ line. The latter is now fixed in the stable repoman version. |
12 |
>> |
13 |
>> Therefore, I am going to remove the remaining CVS headers throughout |
14 |
>> the tree (except for patches, of course) in two days from now. |
15 |
>This was also discussed in August 2015: |
16 |
>Subject: 'Infra plans regarding $Id$ - official answer...' |
17 |
>https://archives.gentoo.org/gentoo-dev/message/d01ce943a9f9404c454c26bdb7efdf0e |
18 |
> |
19 |
>$Id$ is used by Git as well, and I was a strong advocate that expansion |
20 |
>of $Id$ should be ENABLED in the rsync exports, because it allowed |
21 |
>tracing what version of a file was actually in use. |
22 |
> |
23 |
>In the case of Git, $Id$ expands to the blob hash, which can be traced |
24 |
>to a commit trivially, and several of the council members in the 2015 |
25 |
>thread did agree it was useful in that format (but I see no formal vote |
26 |
>was ever taken). |
27 |
> |
28 |
|
29 |
And that's exactly for what I use the $Id$ header. |
30 |
I am completely against removal of this header line. It does _not_ do |
31 |
any harm and I don't understand why people want it to be removed so |
32 |
badly. |
33 |
Now QA again wants to do a questionable action _without_ any approval |
34 |
from neither infra nor council. Sorry guys but this is not how things |
35 |
work. The official answer from infra regarding $Id$ gives enough good |
36 |
examples why this header line should be kept. |
37 |
This $Id$ header line is the only way how I can safely keep official |
38 |
ebuilds and ebuilds from my overlay in sync. I don't like getting my |
39 |
workflows sabotaged and I consider this a pure act of sabotage... |
40 |
|
41 |
How about QA finally starts acting on useful issues or at least do |
42 |
actions that make sense? |
43 |
|
44 |
-- |
45 |
Lars Wendler |
46 |
Gentoo package maintainer |
47 |
GPG: 21CC CF02 4586 0A07 ED93 9F68 498F E765 960E 9B39 |
48 |
|
49 |
Attention! New gpg key! See |
50 |
https://www.gentoofan.org/blog/index.php?/archives/9-New-gpg-keys.html |