From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>
Cc: "'René Scharfe'" <l.s.r@web.de>, git@vger.kernel.org
Subject: RE: [PATCH v2 2/6] Add tar extract install options override in installation processing.
Date: Sat, 20 Jan 2018 15:52:47 -0500 [thread overview]
Message-ID: <01ad01d39230$a41c9b20$ec55d160$@nexbridge.com> (raw)
In-Reply-To: <877esci81l.fsf@evledraar.gmail.com>
On January 20, 2018 3:34 PM, Ævar Arnfjörð Bjarmason
> On Sat, Jan 20 2018, Randall S. Becker jotted:
>
> > I will reissue this particular patch shortly.
>
> It makes sense to base that submission on the next branch instead of master.
> I have a patch queued up there which adds two new tar invocations.
>
> Also re your commit message see the formatting guide in
> Documentation/SubmittingPatches, in particular: instead of:
>
> - Add a brief subject line
>
> - Just make the body be a normal paragraph instead of a bullet-point
> list with one item.
Got it. I've been swapping between contribution styles so got a little confused. I'm going to reissue all of the patches required for the NonStop port later tonight or tomorrow, once the test suite run is finished. I'll take everyone's comments into account for that. Thanks for your (and everyone else's) guidance.
Cheers,
Randall
-- Brief whoami:
NonStop developer since approximately NonStop(211288444200000000)
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2018-01-20 20:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 17:33 [PATCH v2 0/6] Force pipes to flush immediately on NonStop platform randall.s.becker
2018-01-19 17:34 ` [PATCH v2 0/6] Cover Letter for NonStop Port Patches randall.s.becker
2018-01-19 17:34 ` [PATCH v2 1/6] Bypass GCC attributes on NonStop platform where used randall.s.becker
2018-01-19 19:25 ` Stefan Beller
2018-01-19 20:28 ` Ramsay Jones
2018-01-19 21:20 ` Jeff King
2018-01-19 22:43 ` Ramsay Jones
2018-01-19 22:53 ` Randall S. Becker
2018-01-19 17:34 ` [PATCH v2 2/6] Add tar extract install options override in installation processing randall.s.becker
2018-01-20 12:30 ` René Scharfe
2018-01-20 13:44 ` Randall S. Becker
2018-01-20 14:24 ` René Scharfe
2018-01-20 15:35 ` Randall S. Becker
2018-01-20 20:34 ` Ævar Arnfjörð Bjarmason
2018-01-20 20:52 ` Randall S. Becker [this message]
2018-01-19 17:34 ` [PATCH v2 3/6] Define config options required for the HPE NonStop NSX and NSE platforms randall.s.becker
2018-01-19 17:34 ` [PATCH v2 4/6] Force test suite traps to be cleared for NonStop ksh randall.s.becker
2018-01-19 19:55 ` Stefan Beller
2018-01-19 21:27 ` Jeff King
2018-01-19 22:29 ` Randall S. Becker
2018-01-19 23:29 ` Randall S. Becker
2018-01-21 4:07 ` Randall S. Becker
2018-01-19 17:34 ` [PATCH v2 5/6] Bring NonStop platform definitions up to date in git-compat-util.h randall.s.becker
2018-01-19 17:34 ` [PATCH v2 6/6] Add intptr_t and uintptr_t to regcomp.c for NonStop platform randall.s.becker
2018-01-19 19:34 ` [PATCH v2 0/6] Force pipes to flush immediately on " Stefan Beller
2018-01-20 11:10 ` Torsten Bögershausen
2018-01-20 13:23 ` Randall S. Becker
2018-01-22 22:36 ` Junio C Hamano
2018-01-22 22:43 ` Randall S. Becker
2018-01-23 18:13 ` Junio C Hamano
2018-01-23 20:46 ` Randall S. Becker
2018-01-25 3:42 ` Randall S. Becker
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='01ad01d39230$a41c9b20$ec55d160$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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;
as well as URLs for NNTP newsgroup(s).