From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: retrieving a diff from git
Date: Tue, 14 Oct 2008 19:56:36 +0200 [thread overview]
Message-ID: <vpqfxmz5acr.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20081014172048.GW22427@vanheusden.com> (Folkert van Heusden's message of "Tue\, 14 Oct 2008 19\:20\:49 +0200")
Folkert van Heusden <folkert@vanheusden.com> writes:
>> but ... Have you considered using Git for that?
>
> and check out the whole tree using Git? I did consider but then I would
> not have all bells and whistles to generate a Debian kernel package.
You can probably clone the Kernel repository, generate a huge diff
with git diff, and apply it to your Debian tree with patch or
git apply, but if the patch serie is not based on your tree, this
won't help with conflicts.
--
Matthieu
next prev parent reply other threads:[~2008-10-14 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:51 retrieving a diff from git Folkert van Heusden
2008-10-14 17:01 ` Alex Riesen
2008-10-14 17:20 ` Folkert van Heusden
2008-10-14 17:29 ` Alex Riesen
2008-10-14 17:56 ` Matthieu Moy [this message]
2008-10-15 10:12 ` Christian Jaeger
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=vpqfxmz5acr.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=folkert@vanheusden.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.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;
as well as URLs for NNTP newsgroup(s).