From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Branch management
Date: Mon, 17 Apr 2006 10:37:15 +1000 [thread overview]
Message-ID: <874q0tf35w.fsf@zip.com.au> (raw)
In-Reply-To: <8764lzt09d.fsf@laas.fr> (Ludovic Courtès's message of "Tue, 28 Mar 2006 10:57:18 +0200")
I did the dreaded merge. The 1.8 branch now has a tag
branch_release-1-8_last-merged-to-head
as described in the cvs manual, ready for the next merge.
You can see the 1.8 to head diff with
cvs diff -r branch_release-1-8 -r HEAD
The current differences are just version number bumps for 1.9, and
Ludovic's gc sweep stats.
I noticed the 1.8 README still says 1.7.90, I guess that missed
getting updated for the actual 1.8.0. Something to remember for
1.8.1.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-04-17 0:37 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
2006-03-25 23:09 ` Marius Vollmer
2006-03-28 8:57 ` Ludovic Courtès
2006-04-17 0:37 ` Kevin Ryde [this message]
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=874q0tf35w.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).