From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Update the libhttpparser package
Date: Tue, 1 Dec 2015 21:37:34 +0100 [thread overview]
Message-ID: <565E050E.6080104@mind.be> (raw)
In-Reply-To: <1449001232.1893.32.camel@embedded.rocks>
On 01-12-15 21:20, J?rg Krause wrote:
> On Di, 2015-12-01 at 13:21 +0100, Renaud AUBIN wrote:
>> I have resubmitted by figuring out by myself the ad hoc git am
>> processing?
>> Maybe the Contributing chapter could be slightly improved by a
>> section on packages' patching policies?
>>
>> Thank you for your review.
>>
>
> We have a section about patch policy in the Buildroot manual:
> http://nightly.buildroot.org/#patch-policy
But it doesn't say anything about what you have to do when you update a patch.
I'll try to cook something up.
Regards,
Arnout
>
> Best regards
> J?rg Krause
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-12-01 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 8:35 [Buildroot] [PATCH 1/1] Update the libhttpparser package Renaud AUBIN
2015-12-01 10:10 ` Baruch Siach
2015-12-01 12:21 ` Renaud AUBIN
2015-12-01 20:20 ` Jörg Krause
2015-12-01 20:37 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-01 12:15 Renaud AUBIN
2015-12-01 16:50 ` Thomas Petazzoni
2015-12-01 21:59 ` Renaud AUBIN
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=565E050E.6080104@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