gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] Re: Archive configuration recommendations


From: Matthew Palmer
Subject: [Gnu-arch-users] Re: Archive configuration recommendations
Date: Thu, 20 Jan 2005 11:16:34 +1100
User-agent: Mutt/1.5.6+20040907i

On Wed, Jan 19, 2005 at 03:26:37PM -0800, Colin Fox wrote:
> The example in the tutorial for using Star-merge is way too short. It
> seems to assume that the non-mainline developer's archive is in the
> mainline developer's list of archives, which may not be true
> (particularly if the developer is developing on a laptop with a dynamic
> IP). From the wiki:

That's where a mirror comes in.  I have a similar situation for myself -- I
hack on my (frequently disconnected) laptop, and then push changes out to
the mirror on my website for the archives that are likely to be of interest
to anyone else.

Your developers could do a similar thing -- have their own private archive
on their laptops, mirror it to (say) your company webserver (or intranet, or
whatever) and then everyone else can register those mirrors and work from
those.

> "In ordinary use, you invoke star-merge  in the tree you want to merge
> info, providing as an argument the tree you want to merge from:
> 
> 
> ~        % tla get -A address@hidden \
> ~                hello-world--candice--0.1--patch-4 \
> ~                merge-temp
> 
> ~        % tla star-merge address@hidden/hello-world--mainline--0.1
> "
> 
> What is merge-temp? It's not used in the next command, so what's it's
> purpose?

There appears to be a missing command there -- between those two tla
commands there should be a 'cd merge-temp'.  As per the 'get' docs, that
final argument specifies a directory to put the checked-out tree into.

> What happens after the star-merge?

The set of changes between the current working copy and the specified
revision (hello-world--mainline--0.1--patch-<last>) is calculated, and then
applied to the current tree.  You should then review the applied changes,
fix any conflicts, and then commit those changes to your tree, thus
completing the merge.

Caveat: Don't do a merge into a tree with uncommitted changes.  It can be
done, but it's a bit messy.

> What state is the mainline in

Largely irrelevant.  Nothing is changed in the mainline by your merge.

> and what happens when 'candice' wants to re-get the stuff from
> mainline. Does she also star-merge?

candice just got stuff from mainline in the previous commands.  If she wants
to merge again, she re-runs the exact same command, and tla is clever enough
to work out what to merge and what not to re-merge.

The alternate action, where mainline wants candice's changes, is a
star-merge again -- this time, we get hello-world--mainline--0.1 and then
tla star-merge address@hidden/hello-world--candice--0.1.

> (Also, there are lots of typos in the wiki -- "..you want to merge info")

Feel free to fix up any typos you find.  It doesn't look like they're
mandating registration for edits yet.

- Matt

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]