> I thought a simple git fetch would detect deleted branches?
I don't think fetch purges remote refs... Unless something has changed
from the last time I did such an operation.
I like your e-mail.
> The removal of these branches will happen on Monday March 15th.
> After the removal you will
I thought a simple git fetch would detect deleted branches?
Probably wise to send a mail to separate mail to dev@
-
Subject: [NOTICE] All branches will be gone on Monday
We plan to remove up all historic branches in the new solr.git repostiory, and
leave
only the "main" branch.
This will also require people who already made their clones/ forks to
prune their copy of the remote as this isn't done automatically.
git remote prune origin
Other than that -- looks good to me.
D.
On Wed, Mar 10, 2021 at 11:19 PM Jan Høydahl wrote:
>
> Yep, I updated it with a check that
Yep, I updated it with a check that the command succeeded.
Jan
> 10. mar. 2021 kl. 23:09 skrev Ilan Ginzburg :
>
> Any risk in the script that command:
> git push ${REMOTE}
> cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
> errors out in some exotic way (?) but the script
Any risk in the script that command:
git push ${REMOTE}
cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
errors out in some exotic way (?) but the script continues anyway and
proceeds with the delete:
git push ${REMOTE} --delete $BRANCH
On Wed, Mar 10, 2021 at 10:35 PM Jan
Ok, I took a stab at this
We have 113 branches. Here is a script I prepared that will work directly on a
git remote, first creating the tag then deleting the branch.
https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870
In the script I have added the list of branches that I propose to
On Wed, Mar 10, 2021 at 3:17 PM Dawid Weiss wrote:
> ...People work on their local repos these days anyway, it's
> not like everyone pollutes the same workspace.
>
I very much concur. When I got started with git, I treated it closer to
what I was previously more familiar with and created
> We already did this before, see list of existing tags (git tag -l)
I know, I did it, after all... :) This was a move from subversion
though... slightly different. Anyway - if you guys want to proceed
with this, please go ahead, I don't mind. A spring cleaning is needed
every couple of years...
urvives also branch deletes and would have been
detached after master was nuked).
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss
> Sent: Wednesday, March 10, 2021 8:13 PM
> To: Lucene Dev
+1 to tag and remove most if not all branches.
We already did this before, see list of existing tags (git tag -l)
...
history/branches/lucene-solr/lucene_solr_3_1
history/branches/lucene-solr/lucene_solr_3_2
history/branches/lucene-solr/lucene_solr_3_3
I know Uwe wants to purge some (or all) of the existing branches...
I'm not really fond of removing them - this sort of misses the point
of pushing the full mirror from the old repo.
I do understand the will to clean up, however... Maybe we can tag all
existing branches under a common prefix
11 matches
Mail list logo
