Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Gebert <martin.gebert@alpha-bit.de>
To: linux-mips@linux-mips.org
Subject: Re: HOWTO submit patches using WebMail - Help appreciated?
Date: Fri, 18 Jul 2008 16:47:35 +0200	[thread overview]
Message-ID: <4880AD07.2070509@alpha-bit.de> (raw)
In-Reply-To: <20080718143913.GB25491@linux-mips.org>


> I'd like to remind people of the wiki page on this topic at
>
>   http://www.linux-mips.org/wiki/Mailing-patches
>
> It's not been updated in a while and doesn't cover all clients or
> possible solutions so feel free to update it.
>   
Which brings me to a question I've been wondering for some days now: Is 
the [PATCH] prefix in the subject mandatory for a patch proposal being 
noticed by the maintainers?

Martin

  reply	other threads:[~2008-07-18 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 19:59 HOWTO submit patches using WebMail - Help appreciated? Daniel Laird
2008-07-18 13:28 ` Brian Foster
2008-07-18 14:39   ` Ralf Baechle
2008-07-18 14:47     ` Martin Gebert [this message]
2008-07-19  7:15       ` Ralf Baechle
2008-07-21  9:18         ` Martin Gebert
2008-07-24 14:40     ` Adrian Bunk

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=4880AD07.2070509@alpha-bit.de \
    --to=martin.gebert@alpha-bit.de \
    --cc=linux-mips@linux-mips.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