public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Sending in patches
Date: Sun, 10 Jan 2016 21:54:26 +0000	[thread overview]
Message-ID: <1452462866.5665.3.camel@ipfire.org> (raw)

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

Hi,

so in recent times we had many people who have struggled with sending
in patches. The topic comes up every few weeks and I am not aware why
that is. I find this process with "git send-email" very easy and I am
not sure where the problems could be.

So I would like to start a discussion about where the problems are and
maybe that some of you can share their experiences and solutions. What
tools are you using? Do they need special settings?

The goal of that should be that we can add all the required information
to the documentation. Sending in patches should not be this frustration
experience it is at the moment.

  http://wiki.ipfire.org/devel/submit-patches

Best,
-Michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-01-10 21:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 21:54 Michael Tremer [this message]
2016-01-11 20:40 ` Larsen
2016-01-15  1:25   ` Michael Tremer
2016-01-15  8:07     ` IT Superhack
2016-01-15 19:24       ` R. W. Rodolico
2016-01-16 14:45         ` Michael Tremer
2016-01-16 16:07         ` Matthias Fischer
2016-01-16 14:48       ` Michael Tremer
2016-01-16 18:07     ` Larsen
2016-01-17 19:17       ` Michael Tremer
2016-01-28 17:36         ` Larsen
2016-01-29  2:13           ` Michael Tremer
2016-01-12 18:08 ` Matthias Fischer
2016-01-15  1:28   ` Michael Tremer
     [not found] <DUB406-EAS128B6703A1A0778E8A258779CC90@phx.gbl>
2016-01-12 23:51 ` Michael Tremer
2016-01-13  4:39   ` Xaver4all
2016-01-15  1:29     ` Michael Tremer
     [not found] <DUB406-EAS163F3237DC6DE1AF244CD409CCE0@phx.gbl>
2016-01-16 14:53 ` 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=1452462866.5665.3.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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