On 25 Jan 2005 22:51:55 +1100, Matthew Palmer wrote: > > This may be my understanding of how archmag works (hence the 'minor' > severity), but it seems like archmag's partner versions list is missing some > useful branches. In particular, I've got lots of feature branches all > tagged off a trunk, and when I archmag in the trunk I can't see the feature > branches. > > >From the look of the merge feature (unimplemented, I know) I'm supposed to > select a partner version and then merge that into the currently archmag'd > tree -- but, since the feature branches I'd want to merge from aren't > available, I can't. The reverse operation -- merge the current tree into > the selected partner version -- is the only way I can think of that makes > sense, UI-wise, but I would think that the common operation is to merge lots > of branches into one, not merge one branch into lots of different other > places...
TODO file lists this item, i.e. implement "Add" from Partners menu. You are right that it makes sense to mark most of the partner versions as non mergable, this is more or less the purpose of the Kinship field (or maybe we need a new Mergeable field). But as you wrote, the merge feature is not implemented yet, so this field is not used yet. Regards, Mikhael. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
