Cloning with GIT_DEPTH setting is broken
Bug #2023020 reported by
Martin Kopec
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
High
|
Jakub Skunda |
Bug Description
This patch https:/
That commit basically changed from
git clone ... --branch <BRANCH>
to
git clone ...
git checkout <BRANCH>
So it's easy for the desired <BRANCH> to be unavailable if GIT_DEPTH is limited.
It was changed (by 882299) because --branch didn't accept hashes anymore (not exactly sure why) but didn't realize that we might be passing --depth argument there.
We'll need to rework that code so that it accepts both, branches and hashes, as well as depth argument.
Changed in devstack: | |
status: | New → Confirmed |
Changed in devstack: | |
importance: | Undecided → High |
Changed in devstack: | |
assignee: | nobody → Jakub Skunda (jskunda) |
To post a comment you must log in.
Is there a local.conf that I could use to reproduce this behavior? I would like to take a look but I am not knowledgeable enough about how --depth is used by people, so I'd like to reproduce to understand the problem better. Thanks.