Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: No Gnus v0.13 is released
Date: Mon, 21 Feb 2011 20:31:51 -0600	[thread overview]
Message-ID: <874o7wre94.fsf@newsguy.com> (raw)
In-Reply-To: <8739ngc431.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> The last release was (kinda) mistagged, so here's a new release with the
> proper tags.
>
> This release also includes a fix to the nntp bug that some people were
> experiencing, where the new async parallel NNTP fetching code would hang
> if you had some (somewhat degenerate) nntp backend definitions.
>
> Get it by saying
>
>   git clone http://git.gnus.org/gnus.git && cd gnus && git checkout n0-13

That doesn't appear to work here, maybe I've done something wrong?

Using the exact posted command:

,----
| You are in 'detached HEAD' state. You can look around, make experimental
| changes and commit them, and you can discard any commits you make in this
| state without impacting any branches by performing another checkout.
| 
| If you want to create a new branch to retain commits you create, you may
| do so (now or later) by using -b with the checkout command again. Example:
| 
|   git checkout -b new_branch_name
| 
| HEAD is now at f68a008... No Gnus v0.13 is released
`----




  parent reply	other threads:[~2011-02-22  2:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22  0:23 Lars Ingebrigtsen
2011-02-22  0:33 ` Lars Ingebrigtsen
2011-02-22 17:41   ` Ted Zlatanov
2011-02-22  2:31 ` Harry Putnam [this message]
2011-02-22  2:39   ` Lars Ingebrigtsen
2011-02-22  2:53     ` Harry Putnam
2011-02-22  3:25   ` Raphael Kubo da Costa
2011-02-22 17:09 ` Jeremy Hankins
2011-02-22 21:25   ` Steinar Bang
2011-02-22 22:37     ` Jeremy Hankins
2011-02-23  6:39       ` Steinar Bang
2011-02-23  8:19   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874o7wre94.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).