From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Working on master and branch_release-1-8 in the same repository
Date: Mon, 23 Jun 2008 23:48:43 +0100 [thread overview]
Message-ID: <49dd78620806231548q1be29e53w6b7fbbac3c7f5fac@mail.gmail.com> (raw)
In-Reply-To: <87mylcxri9.fsf@gnu.org>
2008/6/23 Ludovic Courtès <ludo@gnu.org>:
>
> Yes. Either cloned from the Savannah repository, or mutually cloned.
> This is what one typically does when using CVS/SVN, but it requires more
> disk space.
Thanks, I'll try things out.
Neil
prev parent reply other threads:[~2008-06-23 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:59 Working on master and branch_release-1-8 in the same repository Neil Jerram
2008-06-10 7:40 ` Ludovic Courtès
2008-06-19 13:25 ` Neil Jerram
2008-06-23 12:30 ` Ludovic Courtès
2008-06-23 22:48 ` Neil Jerram [this message]
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=49dd78620806231548q1be29e53w6b7fbbac3c7f5fac@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).