From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches for Core 113
Date: Wed, 16 Aug 2017 14:43:44 +0100 [thread overview]
Message-ID: <1502891024.2543.28.camel@ipfire.org> (raw)
In-Reply-To: <CAG-tx4Pd89k01j0MRrkxuPGOtNnTbT=NUucRTYJKDjpY1Z-LGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Hi,
On Tue, 2017-08-15 at 22:56 +0200, Wolfgang Apolinarski wrote:
> Hi!
>
> Sorry, I just got the daily digest. I can re-send the patches for
> core 114, if necessary.
let's just work on those patches for now and when ever we are done with
that, we can schedule this for a core update.
Best,
-Michael
>
> Best regards,
> Wolfgang
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2017-08-16 13:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAG-tx4Pd89k01j0MRrkxuPGOtNnTbT=NUucRTYJKDjpY1Z-LGg@mail.gmail.com>]
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=1502891024.2543.28.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