From: Willy Tarreau <w@1wt.eu>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [SOT] GIT usage question
Date: Wed, 11 Oct 2006 20:24:15 +0200 [thread overview]
Message-ID: <20061011182415.GE5050@1wt.eu> (raw)
In-Reply-To: <452D3DFA.6010408@tls.msk.ru>
On Wed, Oct 11, 2006 at 10:54:50PM +0400, Michael Tokarev wrote:
> For quite some time I'm trying to understand if it's possible
> to extract changes from some subsystem's GIT tree compared to
> some version of linux kernel.
>
> For example, let's say I want to see if my SATA controller will
> work with current libata, but without all the pain of trying
> current 2.6.19-pre/rc instabilities. Libata changes are quite
> local for the subsystem, so in theory, or at least how I see
> it, that should be possible.
>
> So I have 3 remote branches in my local GIT tree:
>
> o origin which points to Linus's 2.6.19-pre
> o libata, which is current libata tree
> o 2.6.18 release -- the kernel I'm running right now.
>
> I want to get changes *for libata subsystem* in origin or
> libata (libata is just changes which are on the way to Linus,
> and current difference is very minor), to apply against 2.6.18.
> Ie, in short, changes which went to origin *from* libata.
>
> Is it possible?
If I understand what you want to do, you just have to do this :
$ git-checkout 2.6.18
$ git-pull . libata
This will merge in 2.6.18 everything that's in libata. If you
want to check before what will be merged :
$ git-log 2.6.18..libata
or :
$ git-diff 2.6.18..libata
or also to review the patches one at a time :
$ git-format-patch -k -m 2.6.18..libata
then read all the files.
Hoping it helps
willy
next prev parent reply other threads:[~2006-10-11 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 18:54 [SOT] GIT usage question Michael Tokarev
2006-10-11 18:24 ` Willy Tarreau [this message]
2006-10-11 19:48 ` Michael Tokarev
2006-10-11 19:29 ` Francois Romieu
2006-10-11 19:54 ` Michael Tokarev
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=20061011182415.GE5050@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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