You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #58, PaulPrice fixed lightweight tags such that the username is set to the default mercurial username on the host system, rather than None. This is a much improved interface.
However, I now think it would make more sense to set the username to the default git username and e-mail when pushing to mercurial. At the time that gitifyhg is exporting to mercurial, it knows (or ought to know) more about the state of the git repo than the mercurial one.
Mercurial has no concept of lightweight tags; it is therefore probably more useful for gitifyhg users to use only heavyweight tags. However, there is no reason to explicitly prohibit lightweight tags; we just have to do the heavyweightifying automatically.
The text was updated successfully, but these errors were encountered:
In #58, PaulPrice fixed lightweight tags such that the username is set to the default mercurial username on the host system, rather than None. This is a much improved interface.
However, I now think it would make more sense to set the username to the default git username and e-mail when pushing to mercurial. At the time that gitifyhg is exporting to mercurial, it knows (or ought to know) more about the state of the git repo than the mercurial one.
Mercurial has no concept of lightweight tags; it is therefore probably more useful for gitifyhg users to use only heavyweight tags. However, there is no reason to explicitly prohibit lightweight tags; we just have to do the heavyweightifying automatically.
The text was updated successfully, but these errors were encountered: