From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Is there possible to integrate mtd ubi ubifs latest version in one git tree?
Date: Sat, 12 Apr 2008 13:10:42 +0300 [thread overview]
Message-ID: <1207995042.5965.136.camel@sauron> (raw)
In-Reply-To: <1207994233.5965.124.camel@sauron>
On Sat, 2008-04-12 at 12:57 +0300, Artem Bityutskiy wrote:
> If you do not want to loose UBIFS history, you could do like this
> # cd /home/nanxy/ubifs-v2.6.24
> # git format-patch v2.6.24
> This will give you huge amount of patches, basically all patches which
> we applied to vanilla linux-2.6.24. Now you may apply them to your
> linux-2.6.24.3. The easiest way is to use git-am. But first you have to
> make sure your linux-2.6.24.3 is a git repository. If it is not (you
> downloaded it as a tar.gz file, create a git repository using git
> init-db and then git commit).
>
> # cd /home/nancy/linux-2.6.24.3
> # git init-db
> # git add .
> # git-commit -a
Well, you might as well use quilt, which is an extremely helpful tool.
So you have many patches in /home/nanxy/ubifs-v2.6.24, like
"0061-UBIFS-use-qstr-for-name-length-pairs.patch". What you can do is:
# ls -1 0* > series
# cd /home/nancy/linux-2.6.24.3
# mkdir patches
# mv /home/nanxy/ubifs-v2.6.24/series patches/
# mv /home/nanxy/ubifs-v2.6.24/0* patches/
# quilt push -a
If there are conflicts, it is easier to resolve them with quilt. Often
it is just about "quilt push; quilt refresh".
Ant after you resolved all conflicts, and all patches apply cleanly (use
quilt refresh), you may incorporate all patches to git:
# quilt pop -q
# git reset --hard
# git quiltimport
And you now may delete patches/ and .pc which is private quilt working
directory.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-04-12 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 6:48 Is there possible to integrate mtd ubi ubifs latest version in one git tree? Nancy
2008-04-12 9:57 ` Artem Bityutskiy
2008-04-12 9:59 ` Artem Bityutskiy
2008-04-12 10:10 ` Artem Bityutskiy [this message]
2008-04-14 4:46 ` Nancy
2008-04-14 9:05 ` Artem Bityutskiy
2008-04-15 11:41 ` Jamie Lokier
2008-04-15 11:44 ` Artem Bityutskiy
2008-04-15 15:21 ` Jamie Lokier
2008-04-15 15:41 ` Artem Bityutskiy
[not found] ` <bae050c10804140435v5141dec6qd61b325a4a1ff6ad@mail.gmail.com>
[not found] ` <1208173090.5965.187.camel@sauron>
2008-04-15 12:04 ` Nancy
2008-04-16 6:11 ` Artem Bityutskiy
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=1207995042.5965.136.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@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