From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)
Date: Thu, 24 Jul 2014 15:45:48 -0700 [thread overview]
Message-ID: <xmqqvbqm74v7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <7ACC0F5AD23E4C839D2F819B23DA9564@PhilipOakley> (Philip Oakley's message of "Thu, 24 Jul 2014 23:37:00 +0100")
"Philip Oakley" <philipoakley@iee.org> writes:
>> which still makes me feel hesitant to promote this
>> document without updating its contents, though.
>>
>
> I hadn't viewed it as a 'promotion', rather it was simply ensuring
> access to the guide via the help system, instead of leaving it
> somewhat hidden.
Stale or incorrect pieces of advice that are hidden will not harm
(non-)readers. Making them more available would mean giving them
more chances to do harm ;-).
next prev parent reply other threads:[~2014-07-24 22:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 21:44 What's cooking in git.git (Jul 2014, #04; Tue, 22) Junio C Hamano
2014-07-23 6:56 ` Philip Oakley
2014-07-23 18:10 ` Junio C Hamano
2014-07-24 22:37 ` Philip Oakley
2014-07-24 22:45 ` Junio C Hamano [this message]
2014-07-25 22:08 ` Junio C Hamano
2014-07-28 22:12 ` Philip Oakley
2014-07-30 17:13 ` Everyday contents (was Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)) Junio C Hamano
2014-08-05 20:26 ` Junio C Hamano
2014-08-05 21:00 ` Philip Oakley
2014-08-02 17:28 ` Everday contents (was part of " Philip Oakley
2014-08-03 17:29 ` Everday contents Junio C Hamano
2014-08-03 18:41 ` Philip Oakley
2014-08-04 17:00 ` Junio C Hamano
2014-07-23 14:17 ` What's cooking in git.git (Jul 2014, #04; Tue, 22) Karsten Blees
2014-07-23 18:24 ` Junio C Hamano
2014-07-25 12:30 ` Duy Nguyen
2014-07-29 19:43 ` [RFC/PATCH] Windows tests: let $TRASH_DIRECTORY point to native Windows path Karsten Blees
2014-08-27 13:08 ` Duy Nguyen
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=xmqqvbqm74v7.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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 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.