From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] mongrel2: Add comments to avoid use of github call
Date: Thu, 30 Oct 2014 22:51:22 +0100 [thread overview]
Message-ID: <20141030225122.688a3552@free-electrons.com> (raw)
In-Reply-To: <1413142758-3356-1-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Sun, 12 Oct 2014 21:39:18 +0200, Maxime Hadjinlian wrote:
> As the comment says, we don't want to uses the github helper, as we
> would end up with a generated tarball, which is not the same one as the
> one linked with the releases.
>
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
> v2 -> v3:
> - fix typo
> v1 -> v2:
> - Do not change the URL but add a comments instead
> ---
> package/mongrel2/mongrel2.mk | 2 ++
> 1 file changed, 2 insertions(+)
Applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-30 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 19:39 [Buildroot] [PATCH v3] mongrel2: Add comments to avoid use of github call Maxime Hadjinlian
2014-10-19 8:58 ` Yann E. MORIN
2014-10-30 21:51 ` 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=20141030225122.688a3552@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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