public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Rich Freeman <rich0@gentoo.org>
Cc: gentoo-project@lists.gentoo.org, gentoo-scm@lists.gentoo.org
Subject: Re: [gentoo-project] Council / Git Migration Agenda
Date: Sat, 4 Oct 2014 09:15:04 +0200	[thread overview]
Message-ID: <20141004091504.2dd587af@pomiot> (raw)
In-Reply-To: <CAGfcS_kX76cQX=cMU2OWHFB0nj6MrCCX2xyRfBY8hs=ftGJHkw@mail.gmail.com>

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

Dnia 2014-10-03, o godz. 20:00:24
Rich Freeman <rich0@gentoo.org> napisał(a):

> Starting a new thread for discussion:
> 
> On Thu, Oct 2, 2014 at 7:06 PM, Michał Górny <mgorny@gentoo.org> wrote:
> > Dnia 2014-10-01, o godz. 13:30:55
> > Rich Freeman <rich0@gentoo.org> napisał(a):
> >
> >> On Tue, Sep 30, 2014 at 10:08 PM, Rich Freeman <rich0@gentoo.org> wrote:
> >> > If you'd like to contribute another agenda item, please reply to this email.
> >>
> >> I'll offer up a further topic for the git migration.
> >
> > I think that there are a few issues that the Council may actually want
> > to discuss.
> 
> I was thinking of an additional item also worth consideration.
> 
> So far the general plan has tended to be that we would do a full
> historical git migration, and the last commit would just be the active
> tree, which would then be further cleaned up (remove cvs headers,
> changelogs, switch to thin manifests, etc).
> 
> I was thinking that it might make more sense to just make things
> really simple and ONLY migrate the active tree into the starting git
> repository.  That is, basically take the rsync tree, remove metadata,
> and do a git init.  (Then follow that up with removing changelogs,
> cleaning up cvs headers, and so on.)

Not rsync, 'cvs up -dP [-kk]'. rsync has a lot of cruft and out-of-repo
experiences. Using cvs directly gives us better guarantees about match
between full conversion & snapshot.


-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2014-10-04  7:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04  0:00 [gentoo-project] Council / Git Migration Agenda Rich Freeman
2014-10-04  7:15 ` Michał Górny [this message]
2014-10-05  8:18 ` Dirkjan Ochtman
2014-10-05  9:33   ` Michał Górny
2014-10-06  1:27   ` hasufell
2014-10-06  2:50   ` Seemant Kulleen
2014-10-06  5:48     ` Ulrich Mueller
2014-10-06  8:42       ` Seemant Kulleen
2014-10-06  8:48       ` Michał Górny
2014-10-07  7:57         ` Dirkjan Ochtman
2014-10-07  8:07           ` [gentoo-scm] " Michał Górny
2014-10-07  8:20             ` Ulrich Mueller
2014-10-07  8:26               ` Michał Górny
2014-10-07 10:58           ` Rich Freeman
2014-10-07 11:00             ` Anthony G. Basile
2014-10-07 11:09               ` Rich Freeman
2014-10-09 19:33       ` Tom Wijsman

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=20141004091504.2dd587af@pomiot \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=gentoo-scm@lists.gentoo.org \
    --cc=rich0@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