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>,
	Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Branch management
Date: Tue, 28 Mar 2006 10:57:18 +0200	[thread overview]
Message-ID: <8764lzt09d.fsf@laas.fr> (raw)
In-Reply-To: <87k6aiqfyd.fsf@minimini.mvo.home> (Marius Vollmer's message of "26 Mar 2006 01:09:46 +0200")

Hi,

Marius Vollmer <mvo@zagadka.de> writes:

> It wasn't really planned that way.  We did it differently in 1.6 vs
> HEAD, where we applied patches to both branches simultaneously by
> hand, and we might switch to that mode once HEAD has suffifiently
> diverted from the 1.8 branch.

Hmm, sorry for bothering you, but would it be possible to not wait that
long before merging?  :-)  Especially since (I presume) patching both
branches should not cause any problem for now precisely because they
have not diverged.

Thanks,
Ludovic.


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


  reply	other threads:[~2006-03-28  8:57 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 [this message]
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=8764lzt09d.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    --cc=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).