From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Branch management
Date: Sat, 11 Mar 2006 10:48:13 +0000 [thread overview]
Message-ID: <87irqltfyq.fsf@ossau.uklinux.net> (raw)
Just a heads-up: until I get to any work that isn't appropriate for
the 1.8 branch, I'm planning to make all my commits to the 1.8 branch
only, on the assumption that we will do something later to copy those
changes to CVS head.
Has there yet been any post-1.8 work in CVS? If there hasn't, we
have more options for what that "something later" can be.
I also see a couple of problems with the CVS head branch as it stands.
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.
2. For the same reason, it doesn't have 2006 in its copyrights - which
makes it tedious to compare the 1.8 and head CVS trees.
(To avoid these problems in future, I recommend branching only after
making a .0 release.)
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-03-11 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 10:48 Neil Jerram [this message]
2006-03-14 8:45 ` Branch management 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
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=87irqltfyq.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).