Pass revision to 'hg clone' command when cloning Mercurial repository. #8222
Conversation
manueljacob
force-pushed
the
pass_rev_to_hg_clone
branch
5 times, most recently
from
cccb213 to
980bc65
Compare
manueljacob
force-pushed
the
pass_rev_to_hg_clone
branch
from
980bc65 to
44d3fbe
Compare
|
Some linter CI runs fail because of flake8 warnings in unrelated files. In some environments, flake8 passes. I guess this is unrelated to my changes. |
|
Hi @manueljacob! Thanks for the PR! ^>^ You're correct, that happened because of not-in-this-PR changes. We've merged #8227 which should fix this issue, so rebasing on top of master (or merging master) should fix the linting failures. :) |
pradyunsg
added
C: vcs
|
I am not familiar with svn, so I'm not going to be able to review this PR. :) |
This ensures that only the required changesets are pulled from the server. Some servers don’t advertise all changesets by default. An example is Heptapod, to ensure that changesets with so-called "topics" are only cloned by clients which know how to handle them. Passing the revision enables that these changesets can be cloned anyway. Whether they have a "topic" or not is not relevant to us.
manueljacob
force-pushed
the
pass_rev_to_hg_clone
branch
from
44d3fbe to
5c9e2be
Compare
manueljacob
changed the title
|
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
|
Closing since this is out of date and bitrotten. Please feel free to file a new PR for this! ^>^ |
This ensures that only the required changesets are pulled from the server.
Some servers don’t advertise all changesets by default. An example is
Heptapod, to ensure that changesets with so-called "topics" are only cloned by
clients which know how to handle them. Passing the revision enables that these
changesets can be cloned anyway. Whether they have a "topic" or not is not
relevant to us.