0

If you hg push changeset A into repository myapp-v1 and then do an hg pull and hg merge to merge that into myapp-v2, is there a way in the myapp-v2 repository to identify that the changeset was originally checked into myapp-v1?

Marcus Leon
  • 55,199
  • 118
  • 297
  • 429
  • I think you should use the dedicated Mercurial terms in your question, what do you exactly mean by "check in" ? I suppose `push` by the looks of it. I also think `merge` has nothing to do with what you're describing. Can you provide a list of commands related to your question to clarify things ? – krtek Mar 05 '12 at 14:47
  • In principle no, this is not possible because of the distributed nature of Mercurial. There are no unique identifiers of repositories. What you could do I guess is maintain a central pushlog so that you can find out where a changeset was first pushed to, but you’ll have to build such a system yourself for your specific use-case, and configure it for each repository that you want to participate in it, there is not any kind of generic functionality for this. – Laurens Holst Mar 05 '12 at 15:42
  • Instead of inquiring about this very specific solution, can you describe what specific problem you are trying to solve? Why do you want to identify this? What will you use the information for? That way it would be easier to suggest a solution that suits your needs. – Laurens Holst Mar 05 '12 at 15:47
  • @LaurensHolst: There is no specific reason. At times it is useful to know where a changeset was originally pushed to. It can help gain some context as to the purpose of the changeset. – Marcus Leon Mar 05 '12 at 15:54
  • @Marcus Then, what Lazy Badger said :). – Laurens Holst Mar 05 '12 at 16:32
  • 1
    "purpose of the changeset" must be in commit message and (if branch-per-action policy used) in branch-name. Period – Lazy Badger Mar 05 '12 at 16:45

1 Answers1

4

No. DVCS is DVCS and commited changeset haven't any origin-data after transfer to other clones

Workaround - permanent attributes of each changeset are

  • branch
  • author name

you can use these signs

Lazy Badger
  • 94,711
  • 9
  • 78
  • 110