Message-ID: <41B088F0.1020003@panoramicfeedback.com>
Date: Fri, 03 Dec 2004 10:40:32 -0500
From: Aaron Bentley <abentley@panoramicfeedback.com>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040309)
MIME-Version: 1.0
To: Milan Cvetkovic <milan.cvetkovic@mpathix.com>
Subject: Re: [Gnu-arch-users] Splitting a project to config based
References: <41B0859D.5070208@mpathix.com>
In-Reply-To: <41B0859D.5070208@mpathix.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gnu-arch-users@gnu.org
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 940
Lines: 32
Milan Cvetkovic wrote:
> Suppose I have a big project BASE which I want to split into BCHILD and 
> BLIB, each containing significant portion of files from B, say 50% each.
> 
> I would create a new project CFG with config files.
> 
> Should I tag BCHILD and BLIB of BASE, and remove unneeded files in each?

I'd recommend that approach.  In general, it makes merging easier.

> Or should I tag BCHILD of BASE, since it is the real child of BASE, and 
> create a separate BLIB project with same .arch-id files, as they used to 
> be in BASE?

By default, I'd avoid re-importing files.  Tagging is usually better, 
since it maintains history and ancestry.

Aaron

-- 
Aaron Bentley
Director of Technology
Panometrics, Inc.


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/