From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] call for agenda items, council meeting Mar 12
Date: Mon, 27 Feb 2017 18:09:05 +0100 [thread overview]
Message-ID: <22708.23857.361443.820405@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20170227160544.GA23003@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
>>>>> On Mon, 27 Feb 2017, William Hubbs wrote:
> the Gentoo council will meet again on March 12 at 19:00 utc in the
> #gentoo-council channel on freenode.
> Please respond to this message with any items you would like us to
> add to the agenda to vote on or discuss.
In the 2014-10-14 meeting, there was the following decision under the
"Git Migration Issues" topic:
Can we drop CVS headers post-migration?
Aye: blueness, creffett (proxy for ulm), dberkholz, dilfridge,
radhermit, rich0, williamh
This was again briefly discussed in the 2016-04-10 meeting (following
a discussion in the gentoo-dev mailing list) and in the 2016-11-13
meeting (with respect to a repoman check for the ebuild header).
Since there appear to be doubts how to interpret above mentioned
decision, I would like to ask the Council to clarify the following
points:
a) Are $Id$ and $Header$ lines to be removed in the gentoo repository?
b) Does this only apply to ebuilds and eclasses, or also to other
files in the tree, e.g., metadata, profiles, and files in FILESDIR
other than patches (like init scripts)?
c) Should these lines be removed in one go, or should we enable a
repoman check and have them fade out over time?
d) Should git expansion of $Id$ be enabled (i.e., ident in git
attributes)?
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2017-02-27 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 16:05 [gentoo-project] call for agenda items, council meeting Mar 12 William Hubbs
2017-02-27 17:09 ` Ulrich Mueller [this message]
2017-02-27 17:36 ` Mike Gilbert
2017-02-27 18:16 ` Ulrich Mueller
2017-02-27 23:41 ` William Hubbs
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=22708.23857.361443.820405@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-project@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