From: William Hubbs <williamh@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 17:41:26 -0600 [thread overview]
Message-ID: <20170227234126.GA22564@whubbs1.gaikai.biz> (raw)
In-Reply-To: <22708.27917.807803.995420@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Mon, Feb 27, 2017 at 07:16:45PM +0100, Ulrich Mueller wrote:
> Right, there are many paths to insanity there. That's why we should get
> rid of the whole thing altogether.
I am strongly with ulm on this, we should get rid of $Id$ expansion
altogether, especially since there is a way to generate the hashes that
$Id$ would create from the command line.
If folks want to use the hashes in a work flow some how they can, but
they definitely do not belong in the ebuilds.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2017-02-27 23:41 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
2017-02-27 17:36 ` Mike Gilbert
2017-02-27 18:16 ` Ulrich Mueller
2017-02-27 23:41 ` William Hubbs [this message]
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=20170227234126.GA22564@whubbs1.gaikai.biz \
--to=williamh@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