From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "GitList" <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] Make 'git help everyday' work
Date: Fri, 10 Jan 2014 08:06:28 -0000 [thread overview]
Message-ID: <0AB7145111924BA986B1E172CD293B1D@PhilipOakley> (raw)
In-Reply-To: xmqqppo090m7.fsf@gitster.dls.corp.google.com
From: "Junio C Hamano" <gitster@pobox.com>
>I think we already use a nicer way to set up a page alias to keep
> old links working than making a copy in Documentation/; please mimic
> that if possible.
This was mainly about ensuring that the 'git help' command could access
these extra extra guides that it currently misses. (Tt also misses the
'user-manual', which isn't a man page, but could have a link page to
guide the seeker of truth between 'git help' and the actual user-manual)
The only method I can see for that (via help.c) is to get the filename
format correct. Where you thinking of something else?
>
> It may be overdue to refresh the suggested set of "top 20" commands,
> as things have vastly changed over the past 8 years. Perhaps we
> should do that after reorganizing with something like this series.
Agreed.
> --
next prev parent reply other threads:[~2014-01-10 8:06 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 [this message]
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
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=0AB7145111924BA986B1E172CD293B1D@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox