From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Stefan Beller <sbeller@google.com>,
Junio C Hamano <gitster@pobox.com>,
mlevedahl@gmail.com
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] Cleanup Documentation
Date: Mon, 19 Jun 2017 23:03:45 +0530 [thread overview]
Message-ID: <1497893625.18850.2.camel@gmail.com> (raw)
In-Reply-To: <CAGZ79kbqBXZ5S2TBk6B5gRk+Y-ev2rdgkQZrF-MmHQc0Thj7EQ@mail.gmail.com>
On Sun, 2017-06-18 at 22:50 -0700, Stefan Beller wrote:
> > > diff --git a/Documentation/git-submodule.txt b/Documentation/git-
> > > submodule.txt
> > > index 74bc6200d..9812b0655 100644
> > > --- a/Documentation/git-submodule.txt
> > > +++ b/Documentation/git-submodule.txt
> > > @@ -63,13 +63,7 @@ add [-b <branch>] [-f|--force] [--name <name>]
> > > [--reference <repository>] [--dep
> > > to the changeset to be committed next to the current
> > > project: the current project is termed the "superproject".
> > > +
> > > -This requires at least one argument: <repository>. The optional
> > > -argument <path> is the relative location for the cloned
> > > submodule
> > > -to exist in the superproject. If <path> is not given, the
> > > -"humanish" part of the source repository is used ("repo" for
> > > -"/path/to/repo.git" and "foo" for "host.xz:foo/.git").
> > > -The <path> is also used as the submodule's logical name in its
> > > -configuration entries unless `--name` is used to specify a
> > > logical name.
> > > +This requires at least one argument: <repository>.
> > > +
>
> So we're losing the information how the submodule name is chosen.
I just moved it. I don't think we're losing anything related to how the
name is chosen. Please let me know if I misinterpreted your statement.
> This may be fine as I plan (long term) to make the name an arbitrary
> random
> string (IMHO that reduces confusion as there will be less 'nearly the
> same'
> things)
>
> On the other hand the newly added line
> 'This requires at least one argument: <repository'
> (actually moved, but) is sort of redundant. The notation in the
> argument line
> should make that clear, already?
>
Makes clear sense. Removed it.
> This sounds good, it consolidates all information about [<path>]
> in one paragraph. While at it, maybe let's find another (better)
> substitute for "humanish" as that can be anything(?).
>
> Maybe "the last part of the URL" (without any .git)
>
How about "meaningful"? Put in place it reads like,
If <path> is not given, the meaningful part of the source repository
...
> Please markup the '.gitmodules' either via single quotes or `.
> (or even link to 'gitmodules(5)' )
>
Marked it up using `. Help needed to link to 'gitmodules(5)', as I'm
not sure how to provide alternative text to 'linkgit:'.
> I am undecided if this is really removing (2) unclearness, but the
> (1) redundancy seems fine to me.
>
Sorry about that. The commit message should have been,
...
2. Removed unclear back reference
...
by which I intend to denote the following removal,
> -In either case, the given URL is recorded into .gitmodules for
> -use by subsequent users cloning the superproject.
Note: Will follow up with a patch, soon.
--
Regards,
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
next prev parent reply other threads:[~2017-06-19 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 3:05 [PATCH/RFC] Cleanup Documentation Kaartic Sivaraam
2017-06-19 5:24 ` Junio C Hamano
2017-06-19 5:50 ` Stefan Beller
2017-06-19 17:33 ` Kaartic Sivaraam [this message]
2017-06-19 17:54 ` Stefan Beller
2017-06-20 3:12 ` Kaartic Sivaraam
2017-06-20 16:57 ` Stefan Beller
2017-06-20 17:05 ` Stefan Beller
2017-06-21 3:02 ` [PATCH/FINALRFC] Documentation/git-submodule: cleanup Kaartic Sivaraam
2017-06-21 16:11 ` Junio C Hamano
2017-06-21 17:41 ` Kaartic Sivaraam
2017-06-22 2:51 ` [PATCH/FINAL] " Kaartic Sivaraam
2017-06-22 19:07 ` Junio C Hamano
2017-06-22 19:13 ` Stefan Beller
2017-06-20 18:27 ` [PATCH/RFC] Cleanup Documentation Kaartic Sivaraam
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=1497893625.18850.2.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mlevedahl@gmail.com \
--cc=sbeller@google.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 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.