From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Package moves as repocopies
Date: Wed, 29 Jun 2005 09:57:45 -0400 [thread overview]
Message-ID: <1120053466.13606.235.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <42C1D095.4010501@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Tue, 2005-06-28 at 15:35 -0700, Donnie Berkholz wrote:
> Although this would require a request to someone with shell access to
> the CVS box, it would preserve all the history of the moved packages.
> The loss of history is (IMO) the _primary_ problem of moving packages.
I definitely agree. Losing the history really stinks, especially if you
have to pull something from the Attic. Not only this, but it affects
moves outside of the portage tree, as well. As a good example,
livecd-functions.sh was moved from baselayout to livecd-tools. All the
history was lost. Luckily, it hadn't changed too much, and the broken
part of the script was done by me after the move, so I was able to find
it easily, but what if it had been before the move?
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-29 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 22:35 [gentoo-dev] Package moves as repocopies Donnie Berkholz
2005-06-29 13:57 ` Chris Gianelloni [this message]
2005-07-02 18:47 ` Robin H. Johnson
2005-07-02 23:42 ` Aron Griffis
2005-07-03 1:55 ` Donnie Berkholz
2005-07-02 18:49 ` Robin H. Johnson
2005-07-02 18:59 ` Mike Frysinger
2005-07-04 22:41 ` Robin H. Johnson
2005-07-05 1:34 ` Mike Frysinger
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=1120053466.13606.235.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@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