Re: git-fetch pulls already-pulled objects?

Matt Glazar writes: > On a remote, I have two Git commit objects which point to the same tree > object (created with git commit-tree). What you are expecting _could_ be implemented by exchanging all tree and blob objects sending and receiving sides have and computing the set

Re: git-fetch pulls already-pulled objects?

makes sense (especially for 'git revert HEAD' situations). Thank you for your reply, Junio. -Original Message- From: Junio C Hamano <gits...@pobox.com> Date: Thursday, October 29, 2015 at 10:32 AM To: Matt Glazer <stra...@fb.com> Cc: "git@vger.kernel.org" <git@vg

Re: git-fetch pulls already-pulled objects?

From: Junio C Hamano <gits...@pobox.com> Date: Thursday, October 29, 2015 at 11:42 AM To: Matt Glazer <stra...@fb.com> Cc: "git@vger.kernel.org" <git@vger.kernel.org> Subject: Re: git-fetch pulls already-pulled objects? >Matt Glazar <stra...@fb.com> writes: > >

git-fetch pulls already-pulled objects?

On a remote, I have two Git commit objects which point to the same tree object (created with git commit-tree). If I fetch one of the commits, the commit object (including the tree object) is fetched. If I then fetch the other commit, the tree object (and its dependencies) is fetched *again* (I