From: Nick Clifton <nickc@redhat.com>
To: Nick Alcock <nick.alcock@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 2.40 v2 3/3] libctf: ctf-link outdated input check faulty
Date: Fri, 13 Jan 2023 11:14:21 +0000 [thread overview]
Message-ID: <172e2016-da9b-4d8d-e377-17147181ffe7@redhat.com> (raw)
In-Reply-To: <878ri7pxrw.fsf@esperi.org.uk>
Hi Nick,
>>> It is - but please do this today if you can - I am planning on creating
>>> the release tarballs tomorrow...
>>
>> OK! I'll be pushing to master and 2.40 in twenty minutes or so (final
>
> Hark at the optimism! I reckoned without the traditional last-minute
> massive slowdown of every system one is testing on. I'm only lucky the
> power didn't go out.
Ha- it is always the way. I must apologise too, since I was wrong to
say that I am going to releasing today (Fri 13th). I am actually
planning to make the release tomorrow (Sat 14th), but when I wrote
the original email I had it in my head that it was Friday already.
Wishful thinking I suppose...
> Tests passed, finally: pushed to master and 2.40!
Yay!
Cheers
Nick
prev parent reply other threads:[~2023-01-13 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:00 [PATCH v2 0/3] A few backlogged fixes, and a crash bug Nick Alcock
2023-01-10 13:00 ` [PATCH v2 1/3] ctf: fix various dreadful typos in the ctf_archive format comments Nick Alcock
2023-01-10 13:00 ` [PATCH v2 2/3] libctf: skip the testsuite from inside dejagnu Nick Alcock
2023-01-10 13:00 ` [PATCH v2 3/3] libctf: ctf-link outdated input check faulty Nick Alcock
2023-01-11 17:21 ` [PATCH 2.40 " Nick Alcock
2023-01-12 13:43 ` Nick Clifton
2023-01-12 14:46 ` Nick Alcock
2023-01-12 15:39 ` Nick Alcock
2023-01-13 11:14 ` Nick Clifton [this message]
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=172e2016-da9b-4d8d-e377-17147181ffe7@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=nick.alcock@oracle.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).