Sweetness... this will be most useful. Thanks to both you and Sylvain for responding! On Wed, Apr 28, 2010 at 7:49 PM, Jeff King <peff@xxxxxxxx> wrote: > On Thu, Apr 29, 2010 at 12:54:55AM +0200, Sylvain Rabot wrote: > >> > For example, say I have repository X, which I do a bare clone on to >> > create repository Y for someone else to work on (effectively forking >> > repo X). Is there a way for me to see, from repository X, what commits >> > have been made to repository Y? >> > >> $ git remote update >> $ git log origin/<branch> >> $ gitk origin/<branch> > > That's backwards. He's in the parent repo and wants to see what the > child did. > > The answer is "no, not automatically. Git is fully distributed and > repository X knows nothing about repository Y that was cloned from it". > > But also because git is fully distributed, you can simply treat the > cloned child like any other remote: > > git remote add y /path/to/y > git remote update ;# or just "git fetch y" > git log y/<branch> ;# what happened in y's <branch> > gitk y/<branch>...<branch> ;# differences since y forked > > -Peff > -- 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