On Sat, Mar 14, 2015 at 12:35 PM, Junio C Hamano <gits...@pobox.com> wrote: > Dongcan Jiang <dongcan.ji...@gmail.com> writes: >> What does (you) exactly mean in [1]? The local branch or the local >> remote ref? > > As this operation is not about moving _any_ refs, whether local > branches or remote-tracking branches, any ref that used to point at > commit B before you executed "fetch --deepen" would point at the > same commit after the command finishes.
That would make it harder to implement "fetch --deepen" than the version that moves refs if they are updated. And I think what Dongcan implemented moves refs. From the user point of view, I think it's ok with either version, so the one that's easier to implement wins. > The "you" does not explicitly depict any ref, because the picture is > meant to illustrate _everything_ the repository at the receiving end > of "fetch" has. It used to have two commits, A and B (and the tree > and blob objects necessary to complete these two commits). After > deepening the history by one commit, it then will have commit A^ and > its trees and blobs. > >> [1] http://article.gmane.org/gmane.comp.version-control.git/212950 -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
