From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Email-Date-Format: renamed rootfile
Date: Sat, 19 Sep 2015 10:22:06 +0100 [thread overview]
Message-ID: <1442654526.4141.75.camel@ipfire.org> (raw)
In-Reply-To: <55FC34AF.10307@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
You need to make sure to reply to the list, too.
-Michael
On Fri, 2015-09-18 at 17:58 +0200, Matthias Fischer wrote:
> Hi,
>
> On 18.09.2015 11:17, Michael Tremer wrote:
> > Arne renamed them to perl-... That should fix the problem.
>
> Thanks - I was on the wrong way - but couldn't test this any further.
> During the last builds, my 'Devel' tried to fool me. After clearing
> the
> 'ccache' its working again.
>
> 'next' is up-to-date - in the first attempt build was completed and
> 'iproute2 4.2.0' was build OK. Today I start a new build...
>
> Regards
> Matthias
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-09-19 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55FC34AF.10307@ipfire.org>
2015-09-19 9:22 ` Michael Tremer [this message]
[not found] <55F84DE1.4080809@ipfire.org>
2015-09-18 9:17 ` Michael Tremer
2015-09-19 10:49 ` Matthias Fischer
2015-09-13 18:51 Matthias Fischer
2015-09-14 21:56 ` 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=1442654526.4141.75.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