From: Michael Tokarev <mjt@tls.msk.ru>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [SOT] GIT usage question
Date: Wed, 11 Oct 2006 23:54:10 +0400 [thread overview]
Message-ID: <452D4BE2.6070202@tls.msk.ru> (raw)
In-Reply-To: <20061011192921.GA8345@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Michael Tokarev <mjt@tls.msk.ru> :
> [...]
>> Is it possible?
>
> git diff 2.6.18..origin -- drivers/ata ?
Yeah, -- the idea is to identify which changes are relevant
using some other criteria, not "git tree placement" or something
like that -- example is to use directory as you suggested (plus
relevant includes).
> Experiment with options for rename.
Yeah -- like git-diff-tree -M, I used it before (for this libata stuff
as well), and even wrote a tiny shell wrapper around patch(1) to
apply git-diff-tree -M -generated patch - first pass is to handle
renames in shell, and second pass is to apply the patch itself... ;)
Thanks.
/mjt
prev parent reply other threads:[~2006-10-11 19:54 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
2006-10-11 19:48 ` Michael Tokarev
2006-10-11 19:29 ` Francois Romieu
2006-10-11 19:54 ` Michael Tokarev [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=452D4BE2.6070202@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox