git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: See commits on remote repository

From
BRBryan Richardson <btricha@gmail.com>
Date
Apr 29, 2010, 02:44 UTC
Message-ID
<h2s3f81a4241004281944t574993dfo2af11e451baf98de@mail.gmail.com>
In-Reply-To
<20100429014943.GA4269@coredump.intra.peff.net>

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@peff.net> wrote:
Show 27 quoted lines
> 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
>
Previous: Jeff King
Message 4 of 4 in “See commits on remote repository”
  1. Bryan RichardsonApr 28, 2010
  2. Sylvain RabotApr 28, 2010
  3. Jeff KingApr 29, 2010
  4. Bryan RichardsonApr 29, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.