From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Matt Whiteley <mattwhiteley@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] clone: add disassociate alias to dissociate option
Date: Sat, 21 Feb 2015 02:35:09 -0500 [thread overview]
Message-ID: <20150221073509.GA32548@peff.net> (raw)
In-Reply-To: <xmqqzj87wxck.fsf@gitster.dls.corp.google.com>
On Fri, Feb 20, 2015 at 11:13:47PM -0800, Junio C Hamano wrote:
> >> OPT_BOOL(0, "dissociate", &option_dissociate,
> >> N_("use --reference only while cloning")),
> >> + OPT_BOOL(0, "disassociate", &option_dissociate,
> >> + N_("use --reference only while cloning")),
> >
> > Should this second one be marked as OPT_HIDDEN? I do not think we need
> > to show both in "git clone --help".
>
> For that matter, I am not sure why we want to add this synonym in
> the first place.
>
> http://www.merriam-webster.com/dictionary/dissociate
>
> : to end your relationship with or connection to someone or
> something : to separate (yourself) from someone or something
>
> which is exactly what I wanted the option to achieve.
That is also the definition of disassociate. :) They are both equally
correct here, and some people tend to use one over the other:
http://grammarist.com/usage/dissociate-disassociate/
So I don't think the spirit of the patch is wrong, in that sense. I am
open to the argument that we do not want to get in the habit of
providing every possible synonym, as it would clutter the interface.
This case is a bit more extreme; given the similarity of the two words,
it is easy to use the wrong one. But I do not personally care much
either way.
As a side note, while writing out an explanation of "--reference
--dissociate" recently, Michael (cc'd) and I noticed that it seems quite
verbose to have to specify both options.
By itself, --dissociate does nothing. It _could_ imply --reference (but
right now complains that --reference was not provided and turns itself
off). But if we were to have a single-option version of "reference and
dissociate", I do not think "--dissociate" is the best choice. By itself
it does not mean much (dissociate from _what_?).
I wonder if there is some better word that could become a synonym for
"--reference --dissociate". Maybe "--borrow", but that does not
necessarily carry the implication that the relationship ends as soon as
the clone is done. What is really happening is that we are reusing
objects in order to save bandwidth. Maybe "--reuse-from" would work?
I dunno. I am not extremely happy with any of the suggestions I made,
nor is any of this of extreme importance to me. But I thought I would
mention it while we are on the subject.
-Peff
next prev parent reply other threads:[~2015-02-21 7:35 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 [this message]
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 ` [PATCH] --disassociate alias for --dissociate clone option Eric Sunshine
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=20150221073509.GA32548@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mattwhiteley@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).