From: Pavel Simerda <psimerda@redhat.com>
To: "Pavel Šimerda" <pavlix@pavlix.net>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH 1/7] docs: improve manual pages and help
Date: Mon, 13 Apr 2015 10:05:03 -0400 (EDT) [thread overview]
Message-ID: <1262573367.6639782.1428933903615.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1428933570-8137-1-git-send-email-pavlix@pavlix.net>
----- Original Message -----
> Subject: [PATCH 1/7] docs: improve manual pages and help
Just started using git-send-email. I see I will still need to learn
how to persuade it to change the subject line so that it clear that
the patch is for iproute.
All seven patches are fall iproute and they should generally be
independent of each other.
Cheers,
Pavel
prev parent reply other threads:[~2015-04-13 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 13:59 [PATCH 1/7] docs: improve manual pages and help Pavel Šimerda
2015-04-13 14:05 ` Pavel Simerda [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=1262573367.6639782.1428933903615.JavaMail.zimbra@redhat.com \
--to=psimerda@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pavlix@pavlix.net \
--cc=stephen@networkplumber.org \
/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).