From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] gnupg: Update to 1.4.21
Date: Mon, 22 Aug 2016 14:25:59 -0400 [thread overview]
Message-ID: <1471890359.2153.0.camel@ipfire.org> (raw)
In-Reply-To: <0b7813fe-f1f1-ef1f-659f-a1e9f53d7179@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Don't worry too much. I just notice this and wanted to point it out.
Best,
-Michael
On Mon, 2016-08-22 at 18:39 +0200, Matthias Fischer wrote:
> Hi,
>
> On 22.08.2016 03:49, Michael Tremer wrote:
> >
> > Hi,
> >
> > this won't apply since we have only 1.4.18 in next.
> >
> > Why are our trees out of sync?
>
> Definitely my fault.
>
> It seems that I built 1.4.19 around 27.05.2016 but somehow forgot to
> push.
>
> I'll start all over again with a clean 'gnupg' branch - work in
> progress.
>
> Best,
> Matthias
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-22 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 10:44 Matthias Fischer
2016-08-22 1:49 ` Michael Tremer
2016-08-22 16:39 ` Matthias Fischer
2016-08-22 18:25 ` Michael Tremer [this message]
2016-08-23 16:30 Matthias Fischer
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=1471890359.2153.0.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