well, normally with darcs it's not too bad, it asks you interactively, and you get both tags as choices. not sure what happens when you do a
darcs get --tag=collision though. what I'm hoping for is to be able to tag the hg repo by hand now (using a unique tag name) then to get tailor to skip the offending tag which it's on currently, and then have tailor continue conversion of the rest of the patches. how can I get tailor to skip this tag? On Sat December 15 2007, Martin Marques wrote: > Kevin Geiss escribió: > > Hi, I have a large darcs repo I'm trying to convert to mercurial. it > > was going along fine for about 4 days(!) when it ran into an issue. > > > > apparently darcs will let you have two different tags which happen to > > have the exact same name. but mercurial, upon trying to create a tag > > with a name that already exists, won't do it. (I think there is a > > flag you can give hg to force it to re-tag, but I think that would > > cause the old tag to be moved to the current revision instead of > > creating a new tag) > > > > can anyone think of a workaround? at first I was going to just unpull > > the offending tag from the darcs repo, but I have probably a dozen > > more tags later, so I can't just pull that tag out in any convenient > > way. > > This was discussed on the mercurial list this week, only that it was > related to git and not darcs. > > What I can't understand is why could 2 tags have the same name? The use > of -r TAGNAME wouldn't know what to do. _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
