From: Olaf Hering <olh@suse.de>
To: Brian Gerst <bgerst@didntduck.org>
Cc: git@vger.kernel.org
Subject: Re: how to find outstanding patches in non-linux-2.6 repositories?
Date: Sun, 1 Jan 2006 22:04:39 +0100 [thread overview]
Message-ID: <20060101210429.GA22033@suse.de> (raw)
In-Reply-To: <43B83EBC.9070905@didntduck.org>
On Sun, Jan 01, Brian Gerst wrote:
> Pull the powerpc tree into your local repo, then do something like:
> git-whatchanged master..powerpc
> or
> gitk master..powerpc
This worked for me:
mkdir /dev/shm/x
cd /dev/shm/x
rsync -Ha --delete ~/kernel/git/{powerpc,linux-2.6} .
cd linux-2.6/
cat .git/HEAD > ../start
git-pull /dev/shm/x/powerpc
cat .git/HEAD > ../end
git-format-patch `cat ../start` `cat ../end`
view ????-*
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2006-01-01 21:05 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 [this message]
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=20060101210429.GA22033@suse.de \
--to=olh@suse.de \
--cc=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
/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).