All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.1.0
Date: Sun, 17 Aug 2014 12:25:42 -0700	[thread overview]
Message-ID: <xmqqy4umyl3d.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53F0B7DD.7000605@ramsay1.demon.co.uk> (Ramsay Jones's message of "Sun, 17 Aug 2014 15:10:37 +0100")

Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:

> Are you going to tag and push v2.1.0 to the documentation repos?

I forgot to do the documentation build (which used to be triggered
from post-receive hook at k.org and never had the risk of anybody
forgetting, but it is all manual now---progress X-<) yesterday.  It
is pushed out now.

Thanks.

This is a tangent, but I probahbly should start talking with k.org
folks about arranging to keep the preformatted individual manual
pages (not the tarball that your messages is about) up-to-date.  The
last time I checked, their file-upload procedure these days are
geared towards the use case to upload a handful of tarballs and I
haven't found a way that is not too cumbersome to update a directory
tree with hundreds of individual files.

For now, https://git-htmldocs.googlecode.com/git/git.html would do,
but I'd prefer to have at least two sites to publish to, and k.org
is the natural "other" candidate.

      reply	other threads:[~2014-08-17 19:26 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
2014-08-17 19:25   ` Junio C Hamano [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

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

  git send-email \
    --in-reply-to=xmqqy4umyl3d.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.