From: Kevin Ryde <user42@zip.com.au>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Branch management
Date: Wed, 15 Mar 2006 09:08:41 +1100 [thread overview]
Message-ID: <87lkvcsmqe.fsf@zip.com.au> (raw)
In-Reply-To: <87irqltfyq.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 11 Mar 2006 10:48:13 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> 1. Because it was forked before the 1.8 release, it doesn't contain
> markers in the NEWS or ChangeLogs for when the release happened.
A merge can/will bring those across. I think they should be there,
but maybe they're deliberately only on the branch for some reason.
(It's hard to be too worried about changelogs, but the news file
should describe all releases, no matter whether developed as a
sideline.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-14 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 10:48 Branch management Neil Jerram
2006-03-14 8:45 ` Ludovic Courtès
2006-03-14 19:06 ` Neil Jerram
2006-03-15 8:09 ` Ludovic Courtès
2006-03-15 8:18 ` Neil Jerram
2006-03-14 22:08 ` Kevin Ryde [this message]
2006-03-25 23:09 ` Marius Vollmer
2006-03-28 8:57 ` Ludovic Courtès
2006-04-17 0:37 ` Kevin Ryde
2006-04-18 8:11 ` Ludovic Courtès
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=87lkvcsmqe.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.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).