Kacper Kornet <kornet@xxxxxxxxxxx> writes: > I have just discovered that when I use: > > git fetch --all --depth=<n> > > the history is not deepened. Is the any specific reason for it or is it > a bug? The above is not specific enough to judge if you found a bug or if it is a user error. IIRC, --depth=<n> is not "deepen by <n>", but "make sure I have at least <n> from the updated tip(s)". The shallow-clone hack gives you quite useless (even though it may be internally consistent) semantics if you shallow-cloned way in the past and fetched with --depth after the other side added many more commits than <n>, as you cannot guess what the right value of <n> should be without actually fetching without --depth. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html