public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Bug #10918 was: [ANNOUNCE] Good First Bugs
Date: Mon, 19 Oct 2015 20:36:28 +0200	[thread overview]
Message-ID: <op.x6rna2z5cahio0@honk.fritz.box> (raw)
In-Reply-To: <DUB117-W12478B47C395BD80636DA359C3A0@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

> If you could send me those notes, or even update it on wiki, it would be  
> great benefit.

Here you go:


== Send in a patch ==
* Thunderbird > Compose new mail
* Options > Enable Word Wrap: disable
* Recipient: development(a)lists.ipfire.org <development(a)lists.ipfire.org>
* Subject: [PATCH] <text>
* Body:
First line contains a short description of the patch.

After a blank line, a more precise description follows (if needed; you can  
leave that out for smaller patches). Optionally together with a "Fixes bug  
<number>" in case the patch fixes a bug

Signed-off-by: Your Name <your(a)email.adress>
---

* After the "---" and blank line you put the patch as plain text
* Having sent the mail to the list, you can check  
http://patchwork.ipfire.org/project/ipfire/list
* In case there is a corresponding bug in the bugtracker, you should add a  
note there with the URL to the patch

  parent reply	other threads:[~2015-10-19 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DUB117-W12478B47C395BD80636DA359C3A0@phx.gbl>
2015-10-19 12:05 ` Larsen
2015-10-19 18:36 ` Larsen [this message]
     [not found] <DUB406-EAS3422FCE33A5F4D4F67731149C3A0@phx.gbl>
2015-10-19 20:01 ` Larsen
     [not found] <DUB117-W82174113D55546D54C78F49C3A0@phx.gbl>
2015-10-19 10:34 ` Larsen
     [not found] <DUB117-W1390532CAFBEB3ACC60D1E69C3C0@phx.gbl>
2015-10-17 11:51 ` Michael Tremer

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=op.x6rna2z5cahio0@honk.fritz.box \
    --to=larsen007@web.de \
    --cc=development@lists.ipfire.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