From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Update: To version Apache-2.4.18 and PHP-5.6-17.
Date: Wed, 02 Mar 2016 23:52:37 +0000 [thread overview]
Message-ID: <1456962757.6973.25.camel@ipfire.org> (raw)
In-Reply-To: <813AD0F0-D2D7-4EEE-B1D9-F864605DA9A5@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Hi,
yes please break this up into individual patches that do small changes
at a time.
You can also use RFC instead of PATCH in the headline so you can ask
people to comment on the changes.
-Michael
On Mon, 2016-02-29 at 18:14 +0100, ummeegge wrote:
> Hi all,
> some files are missing and send-email won't deliver the amended
> version
> fatal: /tmp/pQNGd3EHcp/0001-Update-To-version-Apache-2.4.18-and-PHP-
> 5.6-17.patch: 627: patch contains a line longer than 998 characters
> warning: no patches were sent
>
> will push them soon again…
>
> Sorry for that.
>
> Greetings,
>
> Erik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-03-02 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <813AD0F0-D2D7-4EEE-B1D9-F864605DA9A5@ipfire.org>
2016-03-02 23:52 ` Michael Tremer [this message]
2016-03-03 13:47 ` ummeegge
2016-03-03 15:07 ` ummeegge
2016-03-04 12:39 ` 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=1456962757.6973.25.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