From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>,
GitList <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] Make 'git help everyday' work -> relnotes
Date: Tue, 21 Jan 2014 15:28:09 -0800 [thread overview]
Message-ID: <xmqqob34synq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <BA4E87FA92ED4E8FB2C00F013BD7B3FF@PhilipOakley> (Philip Oakley's message of "Tue, 21 Jan 2014 22:25:26 -0000")
"Philip Oakley" <philipoakley@iee.org> writes:
> Determining which is the current release note is possibly more
> problematic, which should be when making the documentation.
Hmmm.... Why?
You are already aware of the stale-notes section, no? Isn't the top
one the latest?
next prev parent reply other threads:[~2014-01-21 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 23:13 [PATCH 0/6] Make 'git help everyday' work Philip Oakley
2014-01-09 23:13 ` [PATCH 1/6] copy everyday.txt to giteveryday.txt Philip Oakley
2014-01-09 23:13 ` [PATCH 2/6] Update giteveryday.txt to fit man page formatting Philip Oakley
2014-01-09 23:13 ` [PATCH 3/6] add giteveryday to the manpages make list Philip Oakley
2014-01-09 23:13 ` [PATCH 4/6] Add deprecation note to old everyday.txt Philip Oakley
2014-01-09 23:13 ` [PATCH 5/6] add 'everyday' to the help --guides list Philip Oakley
2014-01-09 23:13 ` [PATCH 6/6] Update git(1) link to giteveryday Philip Oakley
2014-01-09 23:49 ` [PATCH 0/6] Make 'git help everyday' work Junio C Hamano
2014-01-10 8:06 ` Philip Oakley
2014-01-10 18:09 ` Junio C Hamano
2014-01-10 18:59 ` Philip Oakley
2014-01-11 19:50 ` Philip Oakley
2014-01-10 8:18 ` Stefan Näwe
2014-01-16 21:14 ` [PATCH 0/6] Make 'git help everyday' work -> relnotes Philip Oakley
2014-01-17 11:59 ` Stefan Näwe
2014-01-21 22:25 ` Philip Oakley
2014-01-21 23:28 ` Junio C Hamano [this message]
2014-01-22 0:22 ` Philip Oakley
2014-01-22 0:40 ` Junio C Hamano
2014-01-22 8:33 ` Philip Oakley
2014-01-10 20:19 ` [PATCH 0/6] Make 'git help everyday' work Jonathan Nieder
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=xmqqob34synq.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=stefan.naewe@atlas-elektronik.com \
/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.