From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Do we have a guile-1.8 branch?
Date: Wed, 2 May 2012 18:04:16 -0400 [thread overview]
Message-ID: <CA+U71=Pc0sspP28TOtD4bjDssAo2vHif3-LvZa-_74wErm352g@mail.gmail.com> (raw)
In-Reply-To: <87bom6dz5j.fsf@gnu.org>
> Yes, please remove the ‘release-1.8’ branch.
>
> Something like ‘git push origin :release-1.8’ should work (search for
> “delete” in git-push(1).)
>
> Thanks,
> Ludo’.
Oh, I never knew how to do that. It's done now.
Thanks,
Noah
next prev parent reply other threads:[~2012-05-02 22:04 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
2012-05-02 21:57 ` Ludovic Courtès
2012-05-02 22:04 ` Noah Lavine [this message]
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=Pc0sspP28TOtD4bjDssAo2vHif3-LvZa-_74wErm352g@mail.gmail.com' \
--to=noah.b.lavine@gmail.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).