urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

master
blipvert 2010-09-13 01:44:37 +00:00 committed by Joey Hess
parent 4c74a6c092
commit bed67815fb
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/bugs/git.pm_should_prune_remote_branches_when_fetching.mdwn
View File

@ -7,3 +7,5 @@ Pruning remote branches can be done automatically with the --prune option to "gi
> I'll need more information than that before I add extra processing > I'll need more information than that before I add extra processing
> work to the current git commands it uses. I don't see any errors here > work to the current git commands it uses. I don't see any errors here
> from obsolete remote branches. --[[Joey]] > from obsolete remote branches. --[[Joey]]
Suppose a remote repository contains a branch named "foo", and you fetch from it. Then, someone renames that branch to "foo/bar". The next time you fetch from that repository, you will get an error because the obsolete branch "foo" is blocking the branch "foo/bar" from being created (due to the way git stores refs for branches). Pruning gets around the problem. It doesn't really add much overhead to the fetch, and in fact it can *save* overhead since obsolete branches do consume resource (any commits they point to cannot be garbage collected).