From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] schedule: fix GDB 13 date typos
Date: Tue, 12 Dec 2023 18:14:48 -0500 [thread overview]
Message-ID: <20231212231448.22230-1-vapier@gentoo.org> (raw)
---
schedule/index.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/schedule/index.html b/schedule/index.html
index c051602b1ac7..e3ab7aad006c 100644
--- a/schedule/index.html
+++ b/schedule/index.html
@@ -54,13 +54,13 @@ Fish]" id="archer-logo"/></a>
<tr><td></td><th>CURRENT (GDB 14)</th><th>NEXT (GDB 15)</th>
</tr>
<tr>
-<th>Branch:</th><td>Oct 2023 (2022-10-08)</td><td>Apr 2024</td>
+<th>Branch:</th><td>Oct 2023 (2023-10-08)</td><td>Apr 2024</td>
</tr>
<tr>
<th>Pre-release:</th><td>[as soon as branched]</td><td>[as soon as branched]</td>
</tr>
<tr>
-<th>Release:</th><td>Nov (2022-11-30)</td><td>Apr 2024</td>
+<th>Release:</th><td>Nov (2023-11-30)</td><td>Apr 2024</td>
</tr>
<tr>
<th>reSpin:</th><td>[3 months after release]</td><td>[3 months after release]</td>
@@ -125,11 +125,11 @@ table#history tr > td:nth-child(6) {
<tr> <th>Release</th><th>Estimate</th><th>Schedule</th><th>Actual</th><th>Slip (months)</th><th align=left>Comment</th></tr>
<tr>
-<td>14.1</td><td>2023-11</td><td>2022-11</td><td>2023-12-03</td>
+<td>14.1</td><td>2023-11</td><td>2023-11</td><td>2023-12-03</td>
<td>1</td><td>(no comment)</td></tr>
<tr>
-<td>13.2</td><td>2023-05</td><td>2022-05</td><td>2023-05-27</td>
+<td>13.2</td><td>2023-05</td><td>2023-05</td><td>2023-05-27</td>
<td>0</td><td>(no comment)</td></tr>
<tr>
--
2.43.0
next reply other threads:[~2023-12-12 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:14 Mike Frysinger [this message]
2023-12-15 15:47 ` Tom Tromey
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=20231212231448.22230-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).