From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vong <alexvong1995@gmail.com>
Cc: Andy Wingo <wingo@igalia.com>, Guile User <guile-user@gnu.org>
Subject: Re: [PATCH] Bump version to 2.2.2.
Date: Mon, 13 Nov 2017 17:29:35 +0100 [thread overview]
Message-ID: <87d14mta4w.fsf@gnu.org> (raw)
In-Reply-To: <87y3na89pq.fsf@gmail.com> (Alex Vong's message of "Mon, 13 Nov 2017 23:44:17 +0800")
Alex Vong <alexvong1995@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello!
>>
>> Alex Vong <alexvong1995@gmail.com> skribis:
>>
>>> Tom Jakubowski <tjakubowski@oblong.com> writes:
>>>
>>>> Unsure if this is the right list; if it's the wrong one, then I'm sorry!
>>>>
>>> Thanks for your report, I think you are on the right list!
>>
>> I think Andy, who made the release, has an unpushed patch to the web
>> site that updates the version number *and* adds the news entry for
>> 2.2.2.
>>
> This is werid, I think I can find the news entry here
> <https://www.gnu.org/software/guile/news/gnu-guile-222-released.html>. Any
> idea?
Basically the web site source is in Git (it uses Haunt), and the web
pages are stored separately in CVS (!).
What happened, I think, is that when I added a news entry and pushed the
changes to CVS, that erased the 2.2.2 news entry because it was not in
Git.
Ludo’.
prev parent reply other threads:[~2017-11-13 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 8:52 The website's 2.x series release information is out of date Tom Jakubowski
2017-11-08 15:15 ` [PATCH] Bump version to 2.2.2. (was: The website's 2.x series release information is out of date) Alex Vong
2017-11-13 11:01 ` [PATCH] Bump version to 2.2.2 Ludovic Courtès
2017-11-13 11:36 ` Andy Wingo
2017-11-13 15:44 ` Alex Vong
2017-11-13 16:29 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d14mta4w.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alexvong1995@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@igalia.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).