From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] QUILT helper
Date: Mon, 18 Feb 2013 19:07:56 +0100 [thread overview]
Message-ID: <51226DFC.306@mind.be> (raw)
In-Reply-To: <5122132B.5000402@syscom-instruments.com>
On 18/02/13 12:40, Viallard Anthony wrote:
>>
>> We could add an option to apply-patches.sh to automatically do first
>> steps. We
>> could do:
>> make $PKG-dirclean
>> make CREATE_GIT=1 $PKG-patch
I would make it something like 'make $PKG-prepare-patch'. That gives us
the possibility to later add a PATCH_BACKEND variable that can be set to
git, hg or quilt (or something else).
>> cd build/$PKG-$PKG_VERSION
>> git rebase -i
>> git format-patch initial
>>
>> And with guilt:
>> make $PKG-dirclean
>> make CREATE_GIT=1 $PKG-patch
>> cd build/$PKG-$PKG_VERSION
>> guilt push/pop/refresh
>> guilt export
>>
>> What do you think about it?
>>
>
> Hello J?r?me,
>
> I think using QUILT directly will be the best. Because, we don't need git
> here. We just need a buildroot system to init quilt env, copy patches and
> when the job is done, copy the patches from quilt env to the package
> directory.
I think more people (in particular, the buildroot developers) are
familiar with git (or hg) workflows than quilt workflows.
guilt combines the best features of git and quilt for this particular
purpose, I think (not that I ever used guilt :-). quilt has the
disadvantage that you have to add a file before modifying it - this is
solved by guilt. git has the disadvantage that it is easy to loose your
orientation in the middle of a rebase (with edits) - that is also solved
by guilt.
> I want so much this feature ! I'm the only one here :) ?
I'm also in favour of this feature. In fact, a long time ago I posted a
patch to add a script to do the reverse: create a patch series from a git
repository.
Regards,
Arnout
>
> I began to do some research about how openwrt do that and how we can do
> this in buildroot. But, I'm pretty busy and don't have time to do it now.
> If someone who know internal stuff in buildroot can tell where to do the
> modifications, it will be appreciable.
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-02-18 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 11:18 [Buildroot] QUILT helper Viallard Anthony
2013-01-19 16:36 ` Arnout Vandecappelle
2013-02-14 16:53 ` Jérôme Pouiller
2013-02-18 11:40 ` Viallard Anthony
2013-02-18 18:07 ` Arnout Vandecappelle [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=51226DFC.306@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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