From: Steve James <ste@junkomatic.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcli: new package
Date: Thu, 15 Jan 2015 11:44:02 +0000 [thread overview]
Message-ID: <201501151144.02106.ste@junkomatic.net> (raw)
In-Reply-To: <20150114204001.55afc2c3@free-electrons.com>
On Wednesday 14 Jan 2015 19:40:01 Thomas Petazzoni wrote:
--snip--
> Thanks, applied. I only rewrapped the Config.in help text, and applied
> the rest unchanged.
>
> Thanks!
>
> Thomas
Thanks Thomas. Maybe I'm starting to get the hang of this. Also this one was
simpler because I got my patch into upstream first.
Thanks,
Steve.
prev parent reply other threads:[~2015-01-15 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 14:58 [Buildroot] [PATCH] libcli: new package Steve James
2015-01-14 19:40 ` Thomas Petazzoni
2015-01-15 11:44 ` Steve James [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=201501151144.02106.ste@junkomatic.net \
--to=ste@junkomatic.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.