From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] gitorious helper
Date: Tue, 29 Apr 2014 07:28:42 +0200 [thread overview]
Message-ID: <20140429052841.GB32291@piout.net> (raw)
In-Reply-To: <9a8529fc-851d-4302-9198-67a100db0f26@email.android.com>
On 29/04/2014 at 07:18:08 +0200, Thomas De Schampheleire wrote :
> Alexandre Belloni <alexandre.belloni@free-electrons.com> schreef:
> >After discussing quickly with Thomas, we feel that we can drop it as
> >this would not really help with readability.
>
> Readability wasn't the only reason such helpers were introduced. For github, the download urls changed a few times, and having it coded in only one place made changing this much easier.
> So if that us the only reason I prefer to keep this patch. I'm willing to adopt it by the way...
>
Feel free to adopt it but I'm not sure we can have something easy to use
and elegant.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-29 5:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 16:18 [Buildroot] [RFC PATCH 0/2] gitorious helper Alexandre Belloni
2013-12-25 16:18 ` [Buildroot] [PATCH 1/2] infra: introduce gitorious helper function Alexandre Belloni
2013-12-25 16:18 ` [Buildroot] [PATCH 2/2] packages: use gitorious helper when applicable Alexandre Belloni
2014-01-04 16:20 ` [Buildroot] [RFC PATCH 0/2] gitorious helper Thomas De Schampheleire
2014-01-08 7:54 ` Thomas De Schampheleire
2014-01-10 8:35 ` Thomas Petazzoni
2014-04-29 5:11 ` Alexandre Belloni
2014-04-29 5:18 ` Thomas De Schampheleire
2014-04-29 5:28 ` Alexandre Belloni [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=20140429052841.GB32291@piout.net \
--to=alexandre.belloni@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