From: Eric Sunshine <sunshine@sunshineco.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation/init-db.txt: minor style and synopsys fixes
Date: Thu, 15 Jan 2015 13:00:43 -0500 [thread overview]
Message-ID: <CAPig+cQumvDFc6LuiAWGO4d9LeZmtNr6Os6oRGSrGU8LPsiymA@mail.gmail.com> (raw)
In-Reply-To: <CANCZXo6j6zXX8yrBV=OZpxZPzsf701f79YyQgvWJ+kQ3Dj0qUA@mail.gmail.com>
On Thu, Jan 15, 2015 at 12:08 PM, Alexander Kuleshov
<kuleshovmail@gmail.com> wrote:
> Yes, right,
Etiquette on this list is to avoid top-posting [1].
> how to do it better? Something like: Documentation,
> init-db/init:.....? Or something else?
Simplest would be to split it into two patches: one for
git-init-db.txt and one for git-init.txt.
Also...
>> On Thu, Jan 15, 2015 at 5:31 AM, Alexander Kuleshov
>> <kuleshovmail@gmail.com> wrote:
>>> Subject: Documentation/init-db.txt: minor style and synopsys fixes
>>> This patch constists of two minor changes:
>>>
>>> * line-wrap 'git init-db' synopsis
>>>
>>> * last possible argument '[<directory>]' was missed
>>>
>>> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
>>> ---
>>> +'git init-db' [-q | --quiet] [--bare] [--template=<template_directory>]
>>> + [--separate-git-dir <git-dir>]
>>> + [--shared[=<permissions>]] [<directory>]
Taking Alex's review[2] into consideration:
s/template_directory/template-directory/
[1]: https://lkml.org/lkml/2005/1/11/111
[2]: http://article.gmane.org/gmane.comp.version-control.git/262427
next prev parent reply other threads:[~2015-01-15 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 10:31 [PATCH v2] Documentation/init-db.txt: minor style and synopsys fixes Alexander Kuleshov
2015-01-15 16:50 ` Eric Sunshine
2015-01-15 17:08 ` Alexander Kuleshov
2015-01-15 18:00 ` Eric Sunshine [this message]
2015-01-15 18:55 ` Junio C Hamano
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=CAPig+cQumvDFc6LuiAWGO4d9LeZmtNr6Os6oRGSrGU8LPsiymA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kuleshovmail@gmail.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).