From: Jeff King <peff@peff.net>
To: David Aguilar <davvid@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
git@sfconservancy.org
Subject: Re: Git trademark status and policy
Date: Thu, 25 Oct 2018 01:21:27 -0400 [thread overview]
Message-ID: <20181025052127.GA11460@sigill.intra.peff.net> (raw)
In-Reply-To: <20181024075533.GA11043@gmail.com>
On Wed, Oct 24, 2018 at 12:55:33AM -0700, David Aguilar wrote:
> > So I think we should generally recommend against such generic names
> > during the naming phase. At this point, I'm not sure the pain of
> > changing now is any less than the pain of changing later if and when
> > there's a conflict.
> [...]
>
> Thanks for the recommendation. I'm open to changing the name in a
> future major release. For users that already use the short "dag" name,
> we can transition over to something else if it's relatively short and
> sweet.
Going from my paragraph above, I think it is probably OK to just leave
it for now (unless you prefer to use a major version boundary to do the
change rather than later possibly having to deal with it on a shorter
timeframe).
I have no real opinion on a replacement name. :)
> There's also one more script, but it's never installed in the users's
> $PATH and is more of an internal implementation detail. Git Cola
> includes a GIT_SEQUENCE_EDITOR-compatible "git-xbase" command that
> provides a visual interactive rebase feature. That command should
> probably be renamed to "cola-git-seq-editor" to make that clearer, and
> also to open up the possibility of installing it in bin/ in the future
> since it is useful on its own.
Yeah, agreed. If it's not in the PATH, then it doesn't need to be git-*
at all, does it?
> The rationale for two commands is that worktree diff+commit and history
> inspection are our two primary use-cases. Everything else is provided
> as a sub-command, "git cola rebase", "git cola stash", etc. so there's
> not much pressure to add more top-level names, just these two.
Makes sense.
> Thoughts?
Everything you said seems pretty reasonable to me. Thanks for being
conscientious about the naming issues.
-Peff
next prev parent reply other threads:[~2018-10-25 5:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 2:26 Git trademark status and policy Jeff King
2017-02-21 15:55 ` G. Sylvie Davies
2017-02-21 22:31 ` Jeff King
2017-02-22 1:01 ` G. Sylvie Davies
2018-09-16 10:15 ` David Aguilar
2018-09-17 3:21 ` Jeff King
2018-09-17 9:25 ` Christian Couder
2018-09-18 18:22 ` Jeff King
2018-10-24 7:55 ` David Aguilar
2018-10-25 5:21 ` Jeff King [this message]
2018-09-17 13:58 ` Junio C Hamano
2018-09-18 18:24 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181025052127.GA11460@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=davvid@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).