[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] Re: Using Arch to track non-Arch upstreams
From: |
Miles Bader |
Subject: |
Re: [Gnu-arch-users] Re: Using Arch to track non-Arch upstreams |
Date: |
Fri, 29 Aug 2003 16:49:02 -0400 |
User-agent: |
Mutt/1.3.28i |
On Fri, Aug 29, 2003 at 11:06:35AM -0500, John Goerzen wrote:
> > (2) Where the taglines are _not_ in the canonical sources, and are
>
> This is the scenario I am looking at.
>
> > re-added to the source files whenever you do an import.
>
> I'm not sure what you mean be re-added; are you thinking of something
> like an automated process that iterates over the tree adding taglines?
Yes (my impression is that Xouvert is using something like this; Jonathan if
you're reading this thread, please correct me).
> Because if you are, I think that still wouldn't track renames well.
It wouldn't track _external_ renames, but it would track _internal_ renames;
if you're going to be doing a lot of the latter (as I beleive Xouvert
intends), then you still get a lot of benefit from using taglines.
In such a system, presumably you would always maintain a specific branch for
doing imports, and on that branch the names would remain fairly static
(though it doesn't matter all that much -- whatever method you use to deal
with external renames would basically be the same for explicit tags or for
`re-added' taglines). Because arch deals well with renamed files, merges
from your `external' branch to your mega-renamed internal branches would do
the right thing.
-Miles
--
Somebody has to do something, and it's just incredibly pathetic that it
has to be us. -- Jerry Garcia
Re: [Gnu-arch-users] Using Arch to track non-Arch upstreams, Jan Hudec, 2003/08/29