unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: dsmich@roadrunner.com
Cc: Thien-Thi Nguyen <ttn@gnuvola.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Do we have a guile-1.8 branch?
Date: Tue, 1 May 2012 23:33:10 -0400	[thread overview]
Message-ID: <CA+U71=OLdihgrrV-f3pFU61tyCKxq7f4ogqxhY8peOc0mFV42Q@mail.gmail.com> (raw)
In-Reply-To: <20120501235714.GOXX4.139112.root@cdptpa-web34-z02.mail.rr.com>

Yes, I was just wondering if that was the right place to send Guile
1.8 bugfixes. I went ahead and committed two new fixes to that branch.
They both fix build errors on my system.

Unfortunately, I also made a new branch in our repository called
'release-1.8' because of a git error. It is an exact copy of that
branch. I want to remove the tag from the Savannah repository, because
it is useless and potentially very confusing. Is that the right thing
to do here? If so, is there a way to do it?

Thanks,
Noah

On Tue, May 1, 2012 at 7:57 PM,  <dsmich@roadrunner.com> wrote:
>
> ---- Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
>> () Noah Lavine <noah.b.lavine@gmail.com>
>> () Tue, 1 May 2012 17:15:28 -0400
>>
>>    And if not, would we like one?
>>
>> It would be great to have one.
>
> Yeah, there is one:  http://git.savannah.gnu.org/gitweb/?p=guile.git;a=shortlog;h=refs/heads/branch_release-1-8
>
> I suspect that Andy merely forgot to check that in.
>
> -Dale
>



  reply	other threads:[~2012-05-02  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 21:15 Do we have a guile-1.8 branch? Noah Lavine
2012-05-01 23:25 ` Thien-Thi Nguyen
2012-05-01 23:57   ` dsmich
2012-05-02  3:33     ` Noah Lavine [this message]
2012-05-02 21:57       ` Ludovic Courtès
2012-05-02 22:04         ` Noah Lavine
2012-05-15 19:18           ` Andy Wingo

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='CA+U71=OLdihgrrV-f3pFU61tyCKxq7f4ogqxhY8peOc0mFV42Q@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=dsmich@roadrunner.com \
    --cc=guile-devel@gnu.org \
    --cc=ttn@gnuvola.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).