Thread (4 messages) flat view 4 messages, 3 authors, 2016-08-11

Re: [PATCH] Introduce git-mirror, a tool for exactly mirroring another repository.

From: Jakub Narebski <hidden>
Date: 2016-08-11 19:29:39

Junio C Hamano wrote:
Sergey Vlasov [off-list ref] writes:
 
quoted
BTW, I was thinking about the possibility to save removed refs under,
e.g., refs/old/`date -I`/; maybe even non-fast-forward refs could be
saved there - this will ensure that no object will ever disappear from
the mirror, no matter what is done on the master side.  Obviously, in
this case remote refs like refs/old/* should be filtered.
I do not think that belongs to git-mirror.  It might be better to
have that option in update-ref machinery so that you would even
be protected from a `git branch -d` ran by mistake.
Perhaps just don't remove log when branch is deleted. I tend for example
to be careful when reordering commits on a branch, and use git branch -f
instead of deleting and recreating branch to not lose reflog.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help