From: Andy Wingo <wingo@pobox.com>
To: guile-devel@gnu.org
Subject: Re: Guile 1.8 development
Date: Wed, 01 Mar 2017 18:32:48 +0100 [thread overview]
Message-ID: <87poi0dhrz.fsf@pobox.com> (raw)
In-Reply-To: <87a895chxn.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Wed, 01 Mar 2017 13:14:44 +0100")
On Wed 01 Mar 2017 13:14, Thien-Thi Nguyen <ttn@gnu.org> writes:
> Which git branch is best for continued Guile 1.8 development?
> I know most people have no interest in 1.8, that's fine, just
> kindly humor this slow janitor w/ a normative answer, thanks.
>
> (I guess ‘branch_release-1-8’, but maybe someone knows better.)
Yep, branch_release-1-8.
Happy hacking,
Andy
prev parent reply other threads:[~2017-03-01 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 12:14 Guile 1.8 development Thien-Thi Nguyen
2017-03-01 17:32 ` Andy Wingo [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=87poi0dhrz.fsf@pobox.com \
--to=wingo@pobox.com \
--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).