All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: David Miller <davem@davemloft.net>
Cc: mbizon@freebox.fr, netdev@vger.kernel.org
Subject: Re: [PATCH] sctp: rfc conformance fixes
Date: Wed, 22 Oct 2008 16:01:27 +1100	[thread overview]
Message-ID: <200810221601.27588.jk@ozlabs.org> (raw)
In-Reply-To: <20081021.214725.176087242.davem@davemloft.net>

Hi,

> Jeremy, patchwork doesn't try to interpret the subject line
> at all does it?  My impression is that it simply looked for
> patches in the email posting content and that's it.

That's correct - patchwork uses the content of the mail to determine if 
it contains a patch, not the subject.

Patchwork does make a few modifications to the subject though - mostly 
treatment of []-enclosed prefixes. For example, it removes [PATCH] from 
the subject line - if it's in patchwork, it's a patch :).

So, in this case, the following subjects:

 [RFC] fix breakage
 [PATCH,RFC] fix breakage
 [RFC,PATCH] fix breakage
 [PATCH/RFC] fix breakage

will all be normalised to:

 [RFC] fix breakage

Cheers,


Jeremy


  reply	other threads:[~2008-10-22  5:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  2:08 [PATCH] sctp: rfc conformance fixes Vlad Yasevich
2008-10-22  2:08 ` Vlad Yasevich
2008-10-22  2:08 ` [PATCH 1/4] sctp: Drop ICMP packet too big message with MTU larger than current PMTU Vlad Yasevich
2008-10-22  2:08   ` Vlad Yasevich
2008-10-23  8:00   ` [PATCH 1/4] sctp: Drop ICMP packet too big message with MTU David Miller
2008-10-23  8:00     ` [PATCH 1/4] sctp: Drop ICMP packet too big message with MTU larger than current PMTU David Miller
2008-10-22  2:08 ` [PATCH 2/4] sctp: Add check for the TSN field of the SHUTDOWN chunk Vlad Yasevich
2008-10-22  2:08   ` Vlad Yasevich
2008-10-23  8:00   ` [PATCH 2/4] sctp: Add check for the TSN field of the SHUTDOWN David Miller
2008-10-23  8:00     ` [PATCH 2/4] sctp: Add check for the TSN field of the SHUTDOWN chunk David Miller
2008-10-22  2:08 ` [PATCH 3/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN-PENDING state Vlad Yasevich
2008-10-22  2:08   ` Vlad Yasevich
2008-10-23  8:00   ` [PATCH 3/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN-PENDING David Miller
2008-10-23  8:00     ` [PATCH 3/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN-PENDING state David Miller
2008-10-22  2:08 ` [PATCH 4/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN_RECEIVED state Vlad Yasevich
2008-10-22  2:08   ` Vlad Yasevich
2008-10-23  8:01   ` [PATCH 4/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN_RECEIVED David Miller
2008-10-23  8:01     ` [PATCH 4/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN_RECEIVED state David Miller
2008-10-22  4:05 ` [PATCH] sctp: rfc conformance fixes David Miller
2008-10-22  4:05   ` David Miller
2008-10-22  4:44   ` Maxime Bizon
2008-10-22  4:47     ` David Miller
2008-10-22  5:01       ` Jeremy Kerr [this message]
2008-10-22  5:32         ` Maxime Bizon
2008-10-22  5:35           ` Jeremy Kerr
2008-10-22  6:02             ` Maxime Bizon
2008-10-22 13:03             ` Vlad Yasevich
2008-10-22 22:54               ` Jeremy Kerr
2008-10-22 23:46                 ` David Miller
2008-10-22 23:48                   ` David Miller
2008-10-23  1:24                     ` Vlad Yasevich
2008-10-23  4:06                       ` David Miller
2008-10-23  6:15                         ` Simon Horman
2008-10-23  8:06                           ` David Miller
     [not found]                 ` <48FFBA06.50609@hp.com>
2008-10-23  0:43                   ` Jeremy Kerr
2008-10-23  3:34                     ` Jeremy Kerr
2008-10-23  4:11                       ` David Miller
2008-10-23  5:47                         ` Benjamin Herrenschmidt
2008-10-23  5:54                           ` Jeremy Kerr
2008-10-22  6:12           ` David Miller
2008-10-22 16:48             ` Maxime Bizon
2008-10-22 21:10               ` David Miller
2008-10-22 23:42   ` Vlad Yasevich
2008-10-22 23:42     ` Vlad Yasevich
2008-10-23  4:12     ` David Miller
2008-10-23  4:12       ` David Miller

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=200810221601.27588.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=davem@davemloft.net \
    --cc=mbizon@freebox.fr \
    --cc=netdev@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.