From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Reiserfsprogs
Date: Wed, 29 Jun 2016 23:05:17 +0200 [thread overview]
Message-ID: <20160629230517.611d0821@free-electrons.com> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6EE83277A@ex-mb1.corp.adtran.com>
Hello,
On Wed, 29 Jun 2016 18:20:08 +0000, ANDY KENNEDY wrote:
> Yup, I should. However, with four kids, TKD, Cub Scouts, Boy Scouts,
> Girl Scouts, etc, I cannot find the time for _anything_ (though, this
> is not a complaint, just a reason).
Ah, ah real life issues :-)
> My company blocks SMTP north-bound traffic. And, as you know,
> LookOut! is HORRIBLE for plain text e-mails. I just wanted to
> make sure that it wasn't missing tabs (as I manually have to put
> those into the patch when I paste it into my e-mail since the
> M$ clipboard "helps me" by replacing those EVIL tabs with more
> friendly spaces).
The time you lose fighting with those stupid tools most likely largely
outweighs the time needed to set up once for all a working SMTP system.
> Okay, I'll figure out how to construct that so that on -static
> builds, it does the "right thing" and attempt to push it back
> to Jeff. I was hoping to side step that issue since the
> LIBS=... didn't really hurt anything for dynamic builds as the
> dynamic linker ignores most of those anyway.
This was really just a preference. Mention that it's needed for static
builds, because for dynamic builds, it wasn't needed.
> Another question: Having been dinged in the past for
> resubmission errors, is the current proper way to construct
> the resubmit:
>
> ------------------------------------------------------------
> Subject: [PATCH V2] Reiserfsprogs
No, this should be:
[PATCH v2] reiserfsprogs: new package
git format-patch automatically takes the first line of the commit log
as the e-mail subject.
> and should this be a reply to the original thread or
> a new thread?
A new thread.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-29 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 18:46 [Buildroot] [PATCH] Reiserfsprogs ANDY KENNEDY
2016-06-27 19:03 ` ANDY KENNEDY
2016-06-28 16:18 ` Thomas Petazzoni
2016-06-28 19:49 ` ANDY KENNEDY
2016-06-29 10:04 ` Thomas Petazzoni
2016-06-29 18:20 ` ANDY KENNEDY
2016-06-29 21:05 ` 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=20160629230517.611d0821@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