From: David Greaves <david@dgreaves.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Jonas Fonseca <fonseca@diku.dk>, git@vger.kernel.org
Subject: Re: [RFC] Embedding asciidoc manpages in the cg scripts
Date: Wed, 11 May 2005 23:20:10 +0100 [thread overview]
Message-ID: <4282851A.2010305@dgreaves.com> (raw)
In-Reply-To: <20050511213217.GG22686@pasky.ji.cz>
Petr Baudis wrote:
>> #
>>+# NAME
>>+# ----
>>+# cg-add - add files to a GIT repository
>>
>>
>
>Half of this is useless, too.
>
>I think you should just keep the first paragraph of the files as it is
>now. Don't touch it, just parse it.
>
>
A bit harsh Petr.
Isn't the idea of using an already written tool that you don't _have_ to
parse it?
Where, consistently, do the cg-files have a 1 line summary.
>>+#
>>+# SYNOPSIS
>>+# --------
>>
>>
>No need for this heading either.
>
>
Actually there is :)
asciidoc won't produce a manpage without it.
>>+USAGE="cg-add FILE..."
>>+#
>>+# DESCRIPTION
>>+# -----------
>> # Takes a list of file names at the command line, and schedules them
>> # for addition to the GIT repository at the next commit.
>>+#
>>+# The command will fail if one of the given files does not exist.
>>+#
>>+# cg-add is part of Cogito, an SCM-like toolkit for managing GIT trees.
>>
>>
>
>Useless.
>
>
Yes - if you happen to have written and breathed the code - not so
useless if you're a normal user.
It cogito is ever installed as part of a distro (maybe even by default)
then it would be nice if "man cg-add" actually mentioned it was part of
cogito and git...
>>+#
>>+# OPTIONS
>>+# -------
>>+# No options.
>>
>>
>
>The rest of DESCRIPTION and OPTIONS looks fine.
>
>I'd just expect you to be much less intrusive in the in-file comments
>and do more work when processing the stuff. I'm commenting on how it
>looks inside of the sources - do whatever is necessary when processing
>it to generate a proper-looking manpage from it.
>
>
Having worked hard on being consistent throughout the git docs I'd say
that a little excess verbiage in the comments is a worthwhile price. I
don't think you can worry about performance or anything - these _are_
shell scripts!
Maybe you'd be happier if they were moved to the bottom of the file and
preceded with:
#asciidoc follows
Or if you don't like that then maybe keep them external.
David
--
next prev parent reply other threads:[~2005-05-11 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 1:44 [RFC] Embedding asciidoc manpages in the cg scripts Jonas Fonseca
2005-05-11 21:32 ` Petr Baudis
2005-05-11 22:20 ` David Greaves [this message]
2005-05-11 22:48 ` Petr Baudis
2005-05-13 18:48 ` Jonas Fonseca
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=4282851A.2010305@dgreaves.com \
--to=david@dgreaves.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pasky@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 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.