public inbox for gentoo-scm@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-scm@lists.gentoo.org
Subject: Re: [gentoo-scm] Re: [gentoo-dev] Git Migration: go-live!
Date: Sun, 9 Aug 2015 14:56:43 +0000	[thread overview]
Message-ID: <robbat2-20150809T145506-973165024Z@orbis-terrarum.net> (raw)
In-Reply-To: <CAGfcS_m=s0EY8-kSkPUEDnwbX3sw4CoBpPLqUZy4=oETAFE23g@mail.gmail.com>

On Sun, Aug 09, 2015 at 09:10:30AM -0400, Rich Freeman wrote:
> We shouldn't do anything (besides adapting repoman to the $Id$ format)
> without some discussion first.  However...
> 
> Do we really need to have ANY keywords in our files?  Keyword
> expansion was just a PITA all-around with cvs.  Do we really need to
> embed them in our git files?
> 
> At least git doesn't expand them in the actual repository.
> 
> I'm not really a big fan of any kind of in-band signaling.  I guess
> the one advantage of this is that if you find a file OUTSIDE of a
> repository you know where it came from, but how important is that?
The expansion is ONLY for the rsync export, so that we can identify the
version of the file on a user's system.

When previously discussed, that was a strongly requested item, as
developers DO sometimes ask users to please test rev 1.xyz of an ebuild.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85


      reply	other threads:[~2015-08-09 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 21:39 [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09) Robin H. Johnson
2015-07-02 22:05 ` Rich Freeman
2015-07-03  0:51   ` Robin H. Johnson
2015-07-03  1:26     ` Rich Freeman
2015-08-08 17:47 ` [gentoo-scm] Re: [gentoo-dev] " Robin H. Johnson
2015-08-09  5:36   ` [gentoo-scm] Git Migration: go-live! Robin H. Johnson
     [not found]     ` <55C716C1.5050403@gentoo.org>
     [not found]       ` <20150809093112.GB28996@schiffbauer.net>
2015-08-09 10:02         ` [gentoo-scm] Re: [gentoo-core] [gentoo-dev] " Mike Frysinger
     [not found]           ` <55C725BB.1060500@gentoo.org>
     [not found]             ` <20150809131619.d6f957b30ed09cc5aa35f65c@gentoo.org>
2015-08-09 21:04               ` [gentoo-scm] " Robin H. Johnson
     [not found]     ` <26679488.1voUmlKOLj@arcadia>
2015-08-09 10:46       ` [gentoo-scm] Re: [gentoo-core] " Mike Frysinger
2015-08-09 11:54     ` [gentoo-scm] Re: [gentoo-dev] " Alexey Shvetsov
2015-08-09 12:43       ` Mike Frysinger
2015-08-09 13:10         ` Rich Freeman
2015-08-09 14:56           ` Robin H. Johnson [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=robbat2-20150809T145506-973165024Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-scm@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