git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Richardson <btricha@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Sylvain Rabot <sylvain@abstraction.fr>, git@vger.kernel.org
Subject: Re: See commits on remote repository
Date: Wed, 28 Apr 2010 20:44:10 -0600	[thread overview]
Message-ID: <h2s3f81a4241004281944t574993dfo2af11e451baf98de@mail.gmail.com> (raw)
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:
> 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
>

      reply	other threads:[~2010-04-29  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 22:35 See commits on remote repository Bryan Richardson
2010-04-28 22:54 ` Sylvain Rabot
2010-04-29  1:49   ` Jeff King
2010-04-29  2:44     ` Bryan Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=h2s3f81a4241004281944t574993dfo2af11e451baf98de@mail.gmail.com \
    --to=btricha@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sylvain@abstraction.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).