git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Matt Whiteley <mattwhiteley@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] --disassociate alias for --dissociate clone option
Date: Fri, 20 Feb 2015 17:01:13 -0500	[thread overview]
Message-ID: <CAPig+cTGZohqPRL2OHcaF5bBwED-bhCsZJkp9g00uqJKWfObaA@mail.gmail.com> (raw)
In-Reply-To: <1424459423-11727-1-git-send-email-mattwhiteley@gmail.com>

On Fri, Feb 20, 2015 at 2:10 PM, Matt Whiteley <mattwhiteley@gmail.com> wrote:
> I find the new --dissociate option for clone very helpful but I have a
> hard time with the spelling. It seems reasonable to have an alias since
> one exists for --recursive.

You may be undermining your own argument for inclusion of a new
--dissociate option by citing the aliased "recursive" option.

git-clone's --recursive-submodules was added (see ccdd3da6) for
disambiguation long after --recursive; and not the other way around
with --recursive being more convenient or easier to remember or spell
than --recursive-submodules. The implication of ccdd3da6 is that
--recursive-submodules is favored over --recursive (and perhaps the
latter may some day be deprecated).

      parent reply	other threads:[~2015-02-20 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 19:10 [PATCH] --disassociate alias for --dissociate clone option Matt Whiteley
2015-02-20 19:10 ` [PATCH 1/2] clone: add disassociate alias to dissociate option Matt Whiteley
2015-02-21  6:27   ` Jeff King
2015-02-21  7:13     ` Junio C Hamano
2015-02-21  7:35       ` Jeff King
2015-02-22 18:32         ` Junio C Hamano
2015-02-24  9:06           ` Michael Haggerty
2015-02-24 20:06             ` Junio C Hamano
2015-02-24 22:00               ` Michael Haggerty
2015-02-20 19:10 ` [PATCH 2/2] clone: Realign lines near disassociate option Matt Whiteley
2015-02-20 22:01 ` Eric Sunshine [this message]

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+cTGZohqPRL2OHcaF5bBwED-bhCsZJkp9g00uqJKWfObaA@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=mattwhiteley@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).