Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
No. DVCS is DVCS and commited changeset haven’t any origin-data after transfer to other clones
Workaround – permanent attributes of each changeset are
you can use these signs