git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.1.0
Date: Sun, 17 Aug 2014 15:10:37 +0100	[thread overview]
Message-ID: <53F0B7DD.7000605@ramsay1.demon.co.uk> (raw)
In-Reply-To: <xmqqd2c1z7zu.fsf@gitster.dls.corp.google.com>

On 15/08/14 23:46, Junio C Hamano wrote:
> The latest feature release Git v2.1.0 is now available at the
> usual places.
> 
> The tarballs are found at:
> 
>     https://www.kernel.org/pub/software/scm/git/
> 
> The following public repositories all have a copy of the 'v2.1.0'
> tag and the 'master' branch that the tag points at:
> 
>   url = https://kernel.googlesource.com/pub/scm/git/git
>   url = git://repo.or.cz/alt-git.git
>   url = https://code.google.com/p/git-core/
>   url = git://git.sourceforge.jp/gitroot/git-core/git.git
>   url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
>   url = https://github.com/gitster/git
> 

Are you going to tag and push v2.1.0 to the documentation repos?
(I have been watching the kernel.org documentation repos - should
I be looking elsewhere?)

I stopped building the documentation myself when my documentation
toolchain got a bit old. I have upgraded to Linux Mint 17 since
then, so my toolchain may be up to the job now, so perhaps I should
build it myself. ;-)

ATB,
Ramsay Jones

  parent reply	other threads:[~2014-08-17 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 22:46 [ANNOUNCE] Git v2.1.0 Junio C Hamano
2014-08-15 23:18 ` Theodore Ts'o
2014-08-17 19:19   ` Junio C Hamano
2014-08-17 14:10 ` Ramsay Jones [this message]
2014-08-17 19:25   ` Junio C Hamano

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=53F0B7DD.7000605@ramsay1.demon.co.uk \
    --to=ramsay@ramsay1.demon.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linux-kernel@vger.kernel.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).