From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH 1/3] Auto-generate man pages for all StGit commands
Date: Wed, 10 Sep 2008 22:56:55 +0100 [thread overview]
Message-ID: <b0943d9e0809101456w3c74b86fm9d311fb2594bcf4f@mail.gmail.com> (raw)
In-Reply-To: <20080908210758.1957.664.stgit@yoghurt>
On 08/09/2008, Karl Hasselström <kha@treskal.com> wrote:
> Auto-generate man pages based on the docs that are in each
> stgit/commands/<cmd>.py file. That doc format is extended in order to
> support both brief command help output and manpage text.
Really great stuff. Thanks.
I can see a slight difference in behaviour but I don't have any issue
with it - previously "stg help <cmd>" showed the full description
while "stg <cmd> --help" only the short one.
An additional point on naming - should we use StGIT or StGit? The
original name was StGIT since GIT looked like an acronym. It looks
like now more people name it Git hence our tool moved slowly into
StGit but not everywhere. I personally like StGIT but the last 3
letters should really be the same as the official git (Git, GIT).
--
Catalin
next prev parent reply other threads:[~2008-09-10 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 21:07 [StGit PATCH 0/3] Auto-generate man pages and command list Karl Hasselström
2008-09-08 21:08 ` [StGit PATCH 2/3] asciidoc.conf: Steal updates from git Karl Hasselström
2008-09-08 21:08 ` [StGit PATCH 3/3] Generate command lists automatically Karl Hasselström
2008-09-09 7:17 ` [StGit PATCH] Fixes for auto-generation of man pages Daniel White
2008-09-10 15:56 ` Karl Hasselström
[not found] ` <20080908210758.1957.664.stgit@yoghurt>
2008-09-10 21:56 ` Catalin Marinas [this message]
2008-09-11 6:58 ` [StGit PATCH 1/3] Auto-generate man pages for all StGit commands Karl Hasselström
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=b0943d9e0809101456w3c74b86fm9d311fb2594bcf4f@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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;
as well as URLs for NNTP newsgroup(s).