From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: hannes@stressinduktion.org, catab@embedromix.ro,
netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH v5] IPv6 NAT: Do not drop DNATed 6to4/6rd packets
Date: Sat, 28 Sep 2013 17:24:28 -0700 [thread overview]
Message-ID: <1380414268.11373.3.camel@joe-AO722> (raw)
In-Reply-To: <20130928.155750.1130089685321379918.davem@davemloft.net>
On Sat, 2013-09-28 at 15:57 -0400, David Miller wrote:
> Applied, but Catalin please strictly refer to changes in the following
> precise format:
>
> commit $SHA1_ID ("Commit message header line text")
>
> Because SHA1_IDs are ambiguous, especially when the change in question
> is backported into various -stable branches.
There are now enough commits that using only
8 byte SHA1 IDs generates some collisions so
please use 12 bytes or so of the SHA1.
next prev parent reply other threads:[~2013-09-29 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 10:30 [PATCH] Do not drop DNATed 6to4/6rd packets Catalin(ux) M. BOIE
2013-09-15 13:14 ` Hannes Frederic Sowa
2013-09-22 10:58 ` Catalin(ux) M. BOIE
2013-09-22 17:01 ` Joe Perches
2013-09-23 18:31 ` catab
2013-09-23 18:33 ` [PATCH] Do not drop DNATed 6to4/6rd packets (v3) Catalin(ux) M. BOIE
2013-09-23 18:36 ` [PATCH] Do not drop DNATed 6to4/6rd packets catab
2013-09-23 18:36 ` [PATCH] Do not drop DNATed 6to4/6rd packets (v4) Catalin(ux) M. BOIE
2013-09-23 19:11 ` Joe Perches
2013-09-23 20:04 ` [PATCH v5] IPv6 NAT: Do not drop DNATed 6to4/6rd packets Catalin(ux) M. BOIE
2013-09-24 21:36 ` Hannes Frederic Sowa
2013-09-28 19:57 ` David Miller
2013-09-29 0:24 ` Joe Perches [this message]
2013-09-30 3:05 ` catab
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=1380414268.11373.3.camel@joe-AO722 \
--to=joe@perches.com \
--cc=catab@embedromix.ro \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).