Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcurl: fix building against libressl
Date: Tue, 17 Apr 2018 14:36:25 +0200	[thread overview]
Message-ID: <20180417143625.17ceda76@windsurf.numericable.fr> (raw)
In-Reply-To: <c5a388fe-9d06-15b5-0bc1-a4bf23890b19@mind.be>

Hello,

On Tue, 17 Apr 2018 13:41:08 +0200, Arnout Vandecappelle wrote:

> > I.e:
> > 
> > $ git clone https://github.com/curl/curl.git
> > $ cd curl/
> > $ git checkout curl-7_59_0
> > $ git cherry-pick 7c90c93c0b061da81f69fabdd57125b2783c15fb  
> 
>  Use git cherry-pick -x -s. This will add your Sob right away, and it will
> record the upstream commit from which it was taken.

Aah, didn't about -x, definitely useful!

> > $ git format-patch HEAD^  
> 
>  And here, of course, you need to add -N (well, not in this case since it's just
> a single patch, but in general).

Yes, but indeed since it was a single patch, I omitted the -N.

> > Could you rework your patch by doing this ? I could have done it
> > myself, but I preferred to explain the process for doing it properly :)  
> 
>  This should be added to the manual...

True. Honestly, I find our manual badly organized, and I never find
where things should be added. I'm not against writing documentation
(see my e-mail about the changes to the download infrastructure), but I
never find *where* to put those details into our manual.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-04-17 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 12:39 [Buildroot] [PATCH 1/1] libcurl: fix building against libressl Adam Duskett
2018-04-15 18:43 ` Thomas Petazzoni
2018-04-17 11:41   ` Arnout Vandecappelle
2018-04-17 12:36     ` Thomas Petazzoni [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=20180417143625.17ceda76@windsurf.numericable.fr \
    --to=thomas.petazzoni@bootlin.com \
    --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