[Top][All Lists]

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

Re: [Gnu-arch-users] mixing tag and commit

From: Aaron Bentley
Subject: Re: [Gnu-arch-users] mixing tag and commit
Date: Sun, 28 Mar 2004 18:20:45 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Samuel Tardieu wrote:

"Aaron" == Aaron Bentley <address@hidden> writes:

Aaron> That's permitted by the archive format, and given the amount of
Aaron> effort I've invested in handling that case in the backbuilder,
Aaron> it would be nice to see someone use it.

What about the warning present in the tutorial?
From what I understand, it's a warning about the quality of the implementation at the time the tutorial was written. In the ideal, either
1. it's not possible
2. it's supported

 Usage Caution: As a rule of thumb, your branches should be either
 commit based branches (all revisions after base-0 are created by
 commit ) or tag-based branches (all revisions are created by tag
 ). Commands such as replay , update , and star-merge are based on
From my observations, update does the equivalent of
tla undo $current
tla apply-delta $current $latest
tla redo

All of those should be safe.

It's doubtful that star-merge could behave badly for the case of tagging into the same branch. Perhaps it could behave badly in other cases, by selecting the wrong reference version.

Replay doesn't follow ancestry, AFAIK. It may stop at the most recent continuation. I only replay revisions, not versions, so I wouldn't know. Replay really should follow ancestry, but that means it needs to know what revision to start with, and what revision to stop at.


reply via email to

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