From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E9373139694 for ; Mon, 27 Feb 2017 17:37:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E3B6221C039; Mon, 27 Feb 2017 17:37:00 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AECD021C012 for ; Mon, 27 Feb 2017 17:37:00 +0000 (UTC) Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 72354340C97 for ; Mon, 27 Feb 2017 17:36:59 +0000 (UTC) Received: by mail-qk0-f180.google.com with SMTP id u188so108357040qkc.2 for ; Mon, 27 Feb 2017 09:36:59 -0800 (PST) X-Gm-Message-State: AMke39k77AepYKcB58JsF4QxapLX7fx224i0/QfngoWIirXnSgk2J8opW6oFtzAf2GgZUxn4mBd/jO3ugJ2xog== X-Received: by 10.55.192.70 with SMTP id o67mr13505359qki.35.1488217017319; Mon, 27 Feb 2017 09:36:57 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Received: by 10.200.45.11 with HTTP; Mon, 27 Feb 2017 09:36:36 -0800 (PST) In-Reply-To: <22708.23857.361443.820405@a1i15.kph.uni-mainz.de> References: <20170227160544.GA23003@whubbs1.gaikai.biz> <22708.23857.361443.820405@a1i15.kph.uni-mainz.de> From: Mike Gilbert Date: Mon, 27 Feb 2017 12:36:36 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-project] call for agenda items, council meeting Mar 12 To: gentoo-project@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: f9d243a7-1c88-4b70-9853-195e9072a0a4 X-Archives-Hash: 58f92447de3bc869d22b4467166cb92a On Mon, Feb 27, 2017 at 12:09 PM, Ulrich Mueller wrote: >>>>>> 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)? If $Id$ is to be kept, I think point "d" needs further clarification: in what contexts should ident expansion be enabled? At rsync generation time? In the development repo? (via .gitattributes). Enabling expansion in some places but not others may cause some issues that would necessitate further work to prevent "$Id: xxxxxxx $" strings from being committed in the development repo accidentally. This might mean a repoman check and/or a git hook. I would highly suggest the council familiarize themselves with the git ident attribute from the gitattributes man page before making any decision here.