From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: PSA: Rootfile updates
Date: Wed, 27 Apr 2016 12:59:23 +0100 [thread overview]
Message-ID: <1461758363.10266.197.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
Hello all,
I just would like to remind you that you will have to check for rootfile changes
before sending patches. I will constantly have to fix these which just costs me
unnecessary time.
You will have to rebuild this any way. And I urge you all one again to properly
test your patches before sending them in.
Just be more careful, because correcting these problems later requires way too
much work which could easily be avoided. This is not a race. We care about
quality.
Best,
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-04-27 11:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1461758363.10266.197.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