On Sun, Jan 24, 2021 at 10:59:30PM +0000, Roy Marples wrote: > On 24/01/2021 22:50, Joerg Sonnenberger wrote: > > On Sun, Jan 24, 2021 at 10:16:46PM +0000, Roy Marples wrote: > > > Hi Joerg > > > > > > On 24/01/2021 22:03, Joerg Sonnenberger wrote: > > > > Hello Roy, > > > > isn't repo.tagslist() (and maybe filtering out local tags) already doing > > > > what you want? > > > > > > It is sort of. I use it to get a list of tag and yes, I filter out non > > > globals already. > > > However, it only returns the revision tagged with the name, not which > > > revision created the tag. > > > > Why do you care? > > Because fast-import requires the author and date to create the equivalent tag. > This could be different from the author and date of the commit tagged and if > any commit message is given for the tag, that would likely be different > also. > > Currently to get by, I create a light-weight tag instead, but this lacks any > author or date information and unlike the fast-import tag command is not > versioned in the repository like our global tags. > > But more importantly, why do I care? Because the information that should be > exportable is then lost and I have zero tolerance for lost data.
Well, the point of the question is that it is a not very well defined property. I mean just look at the rules to decide which value is visible for conflicting defitions. tags._updatetags is where the merge rules are defined. The relationship to the commit graph is ...interesting at best. So, no, I don't think "tagger" and "tag time" are properties I would naturally associate with a tag. Joerg _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
