On 3/10/23 06:49, Kevin Risden wrote:
So in the case of https://github.com/apache/solr/pull/571 that would be
concretely:
git fetch origin pull/571/head:pr-571
git checkout pr-571
This would work if https://github.com/apache/solr is cloned. There should
be no need to try to find a merge base and reapply commits.
Even a full re-clone shouldn't take all that long. I would hope Crave
has a lot more bandwidth than I do. 38 seconds for me to clone the repo
from github:
---
sheisey@sheisey-desktop:~/fff$ time git clone
https://github.com/apache/solr.git
Cloning into 'solr'...
remote: Enumerating objects: 1254736, done.
remote: Counting objects: 100% (667/667), done.
remote: Compressing objects: 100% (351/351), done.
remote: Total 1254736 (delta 256), reused 535 (delta 162), pack-reused
1254069
Receiving objects: 100% (1254736/1254736), 462.65 MiB | 20.66 MiB/s, done.
Resolving deltas: 100% (739402/739402), done.
real 0m38.137s
user 1m24.712s
sys 0m8.445s
---
If the repo is already cloned, it should be very quick to reset the
repository and repo to a completely clean state on the main branch, do a
git pull, and then do the steps you outlined above to get the PR. Not
that I know what the right git commands are to do these things.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
