From: David Greaves <david@dgreaves.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
git@vger.kernel.org
Subject: Re: [patch] add simple git documentation
Date: Sun, 08 May 2005 08:35:56 +0100 [thread overview]
Message-ID: <427DC15C.3080208@dgreaves.com> (raw)
In-Reply-To: <20050507113618.GA9495@pasky.ji.cz>
Petr Baudis wrote:
>Dear diary, on Sat, May 07, 2005 at 10:37:12AM CEST, I got a letter
>where David Greaves <david@dgreaves.com> told me that...
>
>
>>Andrew Morton wrote:
>>
>>
>>>Pavel Machek <pavel@ucw.cz> wrote:
>>>
>>>
>>>>This adds short intro to git aimed at kernel hackers.
>>>>
>>>>
>>>OK, but I'm hoping that shortly we'll have something more complete than
>>>this, and your patch might not be a suitable starting point for that.
>>>(Large hint-dropping sounds).
>>>
>>>
>>What are you looking for.
>>
>>For man-page-a-like, have you seen Documentation/core-git.txt in Linus'
>>repository?
>>
>>I'll be working more on that this weekend.
>>
>>
>Are you planning to split it to individual files at some point?
>
>
Yes. I'll see how using asciidoc affects that.
And with Linus vacationing it looks like there'll be time this week.
>(That's what I'd like to do with Documentation/cogito/, speaking of
>manpageness...)
>
>
OK
BTW, whatever happened to perlification - the initial stab I sent you
used the perl/pod approach.
The reason I ask is that that means the docs should/could be initially
written as here-documents within the scripts rather than external manpages.
David
next prev parent reply other threads:[~2005-05-08 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050505102600.GA16387@elf.ucw.cz>
2005-05-07 0:58 ` [patch] add simple git documentation Andrew Morton
2005-05-07 8:37 ` David Greaves
2005-05-07 11:36 ` Petr Baudis
2005-05-08 7:35 ` David Greaves [this message]
2005-05-07 19:56 ` Pavel Machek
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=427DC15C.3080208@dgreaves.com \
--to=david@dgreaves.com \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=pavel@ucw.cz \
/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