unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Branch management
Date: Tue, 14 Mar 2006 09:45:12 +0100	[thread overview]
Message-ID: <87u0a1jtyf.fsf@laas.fr> (raw)
In-Reply-To: <87irqltfyq.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 11 Mar 2006 10:48:13 +0000")

Hello,

Neil Jerram <neil@ossau.uklinux.net> writes:

> 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.

Personally, I've been tracking HEAD (with an own Arch branch) from
before the 1.8 release and the fact that HEAD becomes abandoned in favor
the 1.8 branch isn't very practical to me.  Perhaps other people are in
the same situation?

> 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 posted a few bugfixes, some of which haven't been applied yet, some of
which were applied to HEAD, and some of which were applied to 1.8.  :-)

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-03-14  8:45 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 [this message]
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=87u0a1jtyf.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --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).