From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Josip Rodin <joy@entuzijast.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: git question
Date: Mon, 16 Aug 2010 12:06:32 -0400 [thread overview]
Message-ID: <20100816160632.GE12543@phenom.dumpdata.com> (raw)
In-Reply-To: <20100816115527.GA17397@orion.carnet.hr>
On Mon, Aug 16, 2010 at 01:55:27PM +0200, Josip Rodin wrote:
> On Sat, Aug 14, 2010 at 04:22:03PM +0200, Stefan Kuhne wrote:
> > > You can use git to merge the patches from branch A to branch B.
> >
> > but i need the plain patches for a vanilla tree and other patches.
> > So this patches should come into an patchset.
> >
> > Do i have to make a diff beetwen Konrads tree and a vanilla one?
>
> git diff the last tag from the vanilla branch and his last tag, or his HEAD.
Like this: git diff v2.6.32..origin/pv/pcifront-2.6.32
Thought the latest patches that I've been posting for review are in:
devel/xen-pcifront-0.5 and they are based on top 2.6.35, so you would
do:
git diff v2.6.35..origin/devel/xen-pcifront-0.5
and you would get the one big mega patch for the driver. Thought
don't forget you also need the SWIOTLB/Xen-SWIOTLB stuff (which is now
upstream in 2.6.36-rc0).
To make folks life easier I did setup branches which have all of those
patches in one location. They are:
devel/merge.2.6.34
devel/merge.2.6.35
devel/merge.2.6.35-rc6.t2
pv/merge.2.6.32
pv/merge.2.6.33
>
> You can also git fetch a vanilla tree into the same checkout, and then
> git diff the two branches.
<nods>
next prev parent reply other threads:[~2010-08-16 16:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 9:25 git question Stefan Kuhne
2010-08-14 11:11 ` Vincent Hanquez
2010-08-14 13:15 ` Stefan Kuhne
2010-08-14 14:16 ` Pasi Kärkkäinen
2010-08-14 14:22 ` Stefan Kuhne
2010-08-14 19:34 ` Daniel Stodden
2010-08-16 11:55 ` Josip Rodin
2010-08-16 16:06 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-29 1:49 Git Question Mark Wartman
2018-03-29 1:58 ` Taylor Blau
[not found] ` <15759EC4-0867-44B3-995D-6EC121A6EC4C@gmail.com>
2018-04-01 3:15 ` Taylor Blau
2016-01-20 21:28 GIT Question Draggs, Tori
2016-01-22 16:51 ` Johannes Schindelin
[not found] ` <1E23015B9294604195E5EBA53602E115FCF59F@WDC-VMAILBOXP25.smrcy.com>
2016-01-22 17:08 ` Johannes Schindelin
2016-01-22 17:22 ` Draggs, Tori
2016-01-22 17:58 ` Santiago Torres
2012-02-02 19:41 git question Mark Hounschell
2012-02-02 19:49 ` Jack Stone
2012-02-02 19:57 ` Mark Hounschell
2012-01-23 23:02 chromaticwt zac
2012-01-24 5:11 ` Tirtha Ghosh
2011-12-21 9:19 [can-utils] canbusload: flush output at the end of each cycle Kurt Van Dijck
2011-12-22 6:40 ` Oliver Hartkopp
2012-01-11 11:12 ` Marc Kleine-Budde
2012-01-11 11:18 ` git question Kurt Van Dijck
2012-01-11 11:28 ` Marc Kleine-Budde
2012-01-11 12:22 ` Kurt Van Dijck
2006-02-14 10:04 Jes Sorensen
2006-02-14 13:12 ` Jes Sorensen
2006-02-14 16:56 ` Luck, Tony
2006-02-28 9:51 ` Jes Sorensen
2006-02-28 15:22 ` Luck, Tony
2006-02-28 15:45 ` Jes Sorensen
2006-02-28 15:51 ` Luck, Tony
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=20100816160632.GE12543@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=joy@entuzijast.net \
--cc=xen-devel@lists.xensource.com \
/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.