Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)

From: Philip Oakley <philipoakley@iee.org>
Date: Jul 24, 2014, 22:37 UTC
Message-ID: <7ACC0F5AD23E4C839D2F819B23DA9564@PhilipOakley>
In-Reply-To: <xmqqegxcdjzl.fsf@gitster.dls.corp.google.com>

From: "Junio C Hamano" <gitster@pobox.com>
Sent: Wednesday, July 23, 2014 7:10 PM

Show 25 quoted lines

> "Philip Oakley" <philipoakley@iee.org> writes:
>
>>> * po/everyday-doc (2014-01-27) 1 commit
>>> - Make 'git help everyday' work
>>>
>>> This may make the said command to emit something, but the source is
>>> not meant to be formatted into a manual pages to begin with, and
>>> also its contents are a bit stale.
>>
>>> It may be a good first step in
>>> the right direction, but needs more work to at least get the
>>> mark-up right before public consumption.
>>>
>>> Will hold.
>>>
>>
>> It's not clear to me which bits of mark-up are 'wrong' and must be
>> reworked,
>
> It's been too long since I wrote the above and I left it without
> updates (these comments are by default carried over from one issue
> to the next of "What's cooking" report, unless there is some
> development on the topic).  Now I read the output (admittedly, I
> skimmed only the HTML version), I think the formatting / mark-up is
> fine.

Thanks for the clarification - I hadn't been sure which way to go on the formatting aspect.

>
> I at the same time found various command sequences used there are
> rather classical and there are better ways to do the same with
> modern tools,

I can have a look at the 'standalone' and 'participant' developer command lists but would shy away from any claims about the 'integrator' and 'administrator' roles ;-)

> 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.

-- Philip