Re: how to import tags?

This is the logical sequence of commands that my import script runs. Do these results make sense to anybody? [... many commands, including successful debugsetparents/tag pairs ...] foo.hg$ hg debugsetparents heads(descendants(2785083)) foo.hg$ hg -v tag --force --rev 2785083 MyTag abort:

Re: how to import tags?

On Thu, 24 May 2018 16:35:31 -0400, Hollis Blanchard wrote: On 05/24/2018 11:38 AM, Augie Fackler wrote: On May 24, 2018, at 2:20 PM, Hollis Blanchard > wrote: On 05/23/2018 03:15 PM, Hollis

Re: how to import tags?

> On May 24, 2018, at 4:35 PM, Hollis Blanchard > wrote: > > On 05/24/2018 11:38 AM, Augie Fackler wrote: >> >> >>> On May 24, 2018, at 2:20 PM, Hollis Blanchard >>> wrote: >>> >>> On 05/23/2018 03:15 PM, Hollis Blanchard wrote:

Re: how to import tags?

On 05/24/2018 11:38 AM, Augie Fackler wrote: On May 24, 2018, at 2:20 PM, Hollis Blanchard > wrote: On 05/23/2018 03:15 PM, Hollis Blanchard wrote: 2. Commit tags as children of the correct head. I don't see a 'tag' cmdline

Re: how to import tags?

> On May 24, 2018, at 2:20 PM, Hollis Blanchard > wrote: > > On 05/23/2018 03:15 PM, Hollis Blanchard wrote: >> >> 2. Commit tags as children of the correct head. >> >> I don't see a 'tag' cmdline option for this, though: the parent commit is >> the parent of

Re: how to import tags?

On 05/23/2018 03:15 PM, Hollis Blanchard wrote: 2. Commit tags as children of the correct head. I don't see a 'tag' cmdline option for this, though: the parent commit is the parent of the working directory, without an ability to override. That means I would need to keep working directories

how to import tags?

I run a mirror from Perforce into Mercurial. I use p4fastimport to do the actual conversion, but it doesn't handle P4's labels for me, so I have to look them up and commit them later. Also, my hg repositories are bare (no working directory). When I import tags, after the regular commits, I