From: Linus Torvalds <torvalds@osdl.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, 1 Jan 2006 15:09:54 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601011452230.3668@g5.osdl.org> (raw)
In-Reply-To: <20060101200121.GA20633@suse.de>
On Sun, 1 Jan 2006, 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".
First, get a kernel tree, let's say that you just get the standard one
and thus my head will be in "origin" (and perhaps HEAD too, unless you
decide to do some stuff of your own). Then just do something like
git fetch \
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git \
master:powerpc
which gets the master branch from the powerpc.git tree into your "powerpc"
branch (or set up a .git/remotes/powerpc thing if you expect to do more of
this).
Then you can just do
gitk origin..powerpc
(or "git log" or "git-whatchanged -p" instead of "gitk") to see the
commits that are in powerpc but not in "origin".
Linus
prev parent reply other threads:[~2006-01-01 23:10 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
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 ` Linus Torvalds [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=Pine.LNX.4.64.0601011452230.3668@g5.osdl.org \
--to=torvalds@osdl.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 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).