From: Brian Gerst <bgerst@didntduck.org>
To: Olaf Hering <olh@suse.de>
Cc: git@vger.kernel.org
Subject: Re: how to find outstanding patches in non-linux-2.6 repositories?
Date: Sun, 01 Jan 2006 15:42:36 -0500 [thread overview]
Message-ID: <43B83EBC.9070905@didntduck.org> (raw)
In-Reply-To: <20060101200121.GA20633@suse.de>
Olaf Hering wrote:
> How do I get a list of commits in the 'powerpc' tree, which are not part
> of the 'linux-2.6' tree? The git tutorial has a section 'Working with
> Others', but the examples dont work for me. Probably because
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git has
> no info that it is not the "mainline tree".
> All I need is a list of individual commits in that tree, which are not
> (yet) in "mainline". I could get them also from the ozlabs mailing
> lists, for the few patches I need. But it would be better if there is
> some sort of automated way to extract a list of differences between two
> trees.
>
Pull the powerpc tree into your local repo, then do something like:
git-whatchanged master..powerpc
or
gitk master..powerpc
--
Brian Gerst
next prev parent reply other threads:[~2006-01-01 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 20:01 how to find outstanding patches in non-linux-2.6 repositories? Olaf Hering
2006-01-01 20:42 ` Brian Gerst [this message]
2006-01-01 21:04 ` Olaf Hering
2006-01-01 21:32 ` Johannes Schindelin
2006-01-03 19:11 ` how to find outstanding patches in non-linux-2.6 repositories ? Jon Loeliger
2006-01-03 19:21 ` Marco Roeland
2006-01-03 19:35 ` Andreas Ericsson
2006-01-04 1:26 ` Tom Prince
2006-01-03 19:41 ` Linus Torvalds
2006-01-01 23:09 ` how to find outstanding patches in non-linux-2.6 repositories? Linus Torvalds
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=43B83EBC.9070905@didntduck.org \
--to=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--cc=olh@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.