From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Misc consistency updates
Date: Mon, 02 Aug 2010 17:44:02 +0200 [thread overview]
Message-ID: <4C56E7C2.3000306@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1008021711160.13406@obet.zrqbmnf.qr>
On 02.08.2010 17:11, Jan Engelhardt wrote:
> On Monday 2010-08-02 16:59, Patrick McHardy wrote:
>> On 23.07.2010 21:36, Jan Engelhardt wrote:
>>> The following changes since commit 5031b4199192c6643b5c550523fc5c09578264e1:
>>>
>>> Merge branch 'master' into iptables-next (2010-07-23 16:16:11 +0200)
>>>
>>> are available in the git repository at:
>>>
>>> git://dev.medozas.de/iptables master
>>>
>>> Jan Engelhardt (5):
>>> doc: let man(1) autoalign the text in xt_cpu
>>> doc: remove extra empty line from xt_cpu
>>> doc: minimal spelling updates to xt_cpu
>>> all: consistent syntax use in struct option
>>> doc: consistent use of markup
>>
>> xt_cpu is contained in the iptables-next branch, is that where you want
>> me to apply these patches?
>
> Yes indeed.
Pulled, thanks Jan.
prev parent reply other threads:[~2010-08-02 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 19:36 Misc consistency updates Jan Engelhardt
2010-07-23 19:36 ` [PATCH 1/5] doc: let man(1) autoalign the text in xt_cpu Jan Engelhardt
2010-07-23 19:36 ` [PATCH 2/5] doc: remove extra empty line from xt_cpu Jan Engelhardt
2010-07-23 19:36 ` [PATCH 3/5] doc: minimal spelling updates to xt_cpu Jan Engelhardt
2010-07-23 19:36 ` [PATCH 4/5] all: consistent syntax use in struct option Jan Engelhardt
2010-07-23 19:36 ` [PATCH 5/5] doc: consistent use of markup Jan Engelhardt
2010-08-02 14:59 ` Misc consistency updates Patrick McHardy
2010-08-02 15:11 ` Jan Engelhardt
2010-08-02 15:44 ` Patrick McHardy [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=4C56E7C2.3000306@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.