From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inadyn: bump to version 1.99.11
Date: Thu, 16 Oct 2014 13:59:44 -0300 [thread overview]
Message-ID: <543FF980.3090406@zacarias.com.ar> (raw)
In-Reply-To: <20141016185425.7ea20c68@free-electrons.com>
On 10/16/2014 01:54 PM, Thomas Petazzoni wrote:
> There's a mix of tabs and spaces being used in the added lines.
I normally do tabs and my added lines do that, didn't see there were
spaces in there before, i'll convert everything to tabs.
Regards.
prev parent reply other threads:[~2014-10-16 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 16:25 [Buildroot] [PATCH] inadyn: bump to version 1.99.11 Gustavo Zacarias
2014-10-16 16:54 ` Thomas Petazzoni
2014-10-16 16:59 ` Gustavo Zacarias [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=543FF980.3090406@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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