Closed GoogleCodeExporter closed 9 years ago
Original comment by sstrickr...@googlemail.com
on 2 May 2015 at 1:25
This issue was closed by revision 881ef0973391.
Original comment by sstrickr...@googlemail.com
on 2 May 2015 at 1:44
I see another instance of "fetch". It's format could be:
20bf36205074f9c714a3bd98fe6a06e0087f574a
31f28cbcd4e072c15cca3956e5841895df16bd6c Dummy author <a@dummy.email>
1430093730 +0000 fetch origin +refs/heads/*:refs/heads/*: forced-update
Would this patch handle it correctly?
Original comment by danny0...@gmail.com
on 5 May 2015 at 2:43
@danny0838
> I see another instance of "fetch". It's format could be:
> 20bf36205074f9c714a3bd98fe6a06e0087f574a
31f28cbcd4e072c15cca3956e5841895df16bd6c Dummy author <a@dummy.email>
1430093730 +0000 fetch origin +refs/heads/*:refs/heads/*: forced-update
How do you see it? (the exact steps)
Original comment by yuelinho...@gmail.com
on 5 May 2015 at 3:20
Simply add a remote repo and run:
git fetch origin +refs/heads/*:refs/heads/*
Each local ref updated would be added a reflog entry.
Original comment by danny0...@gmail.com
on 5 May 2015 at 3:26
> git fetch origin +refs/heads/*:refs/heads/*
Do you mean "git fetch origin +refs/heads/*:refs/remotes/origin/*"?
Original comment by yuelinho...@gmail.com
on 5 May 2015 at 3:42
NO. It's "git fetch origin +refs/heads/*:refs/heads/*", which is meant to
mirror remote branches to corresponding local branch, and after that the reflog
of any local branch are changed.
To put it aside, if we run "git fetch origin
+refs/heads/*:refs/remotes/origin/*", the reflog of any remote-tracking branch
will still have an entry "fetch origin +refs/heads/*:refs/remotes/origin/*".
Original comment by danny0...@gmail.com
on 5 May 2015 at 6:10
This issue was closed by revision 71e46c7b2f69.
Original comment by sstrickr...@googlemail.com
on 8 May 2015 at 7:01
This issue was closed by revision 881ef0973391.
Original comment by sstrickr...@googlemail.com
on 15 May 2015 at 8:06
This issue was closed by revision 71e46c7b2f69.
Original comment by sstrickr...@googlemail.com
on 15 May 2015 at 8:06
This issue was closed by revision 881ef0973391.
Original comment by sstrickr...@googlemail.com
on 16 May 2015 at 2:59
This issue was closed by revision 71e46c7b2f69.
Original comment by sstrickr...@googlemail.com
on 16 May 2015 at 2:59
Original issue reported on code.google.com by
danny0...@gmail.com
on 2 May 2015 at 12:56