public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
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 19:16:45 +0100	[thread overview]
Message-ID: <22708.27917.807803.995420@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAJ0EP40++Xb=eOzc_ceirn0EXLwPyGXHpmR7KRAFGXWODhsGqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

>>>>> On Mon, 27 Feb 2017, Mike Gilbert wrote:

>> 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.

Right, there are many paths to insanity there. That's why we should get
rid of the whole thing altogether.

A content tracker should faithfully keep track of the files committed,
but not modify their contents. Even CVS didn't reduce $Id: something$
to $Id$, but kept the original version in the repository [1].

Ulrich

[1] http://cvsman.com/cvs-1.12.12/cvs_99.php#SEC99

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2017-02-27 18:17 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 [this message]
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.27917.807803.995420@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