From: jdl@freescale.com
To: git@vger.kernel.org
Subject: Re: Should Cogito scripts be renamed?
Date: Thu, 15 Sep 2005 19:07:04 -0500 [thread overview]
Message-ID: <E1EG3ku-0005hU-Eb@jdl.com> (raw)
In-Reply-To: <20050915234607.GA10867@pasky.or.cz>
So, like, the other day Petr asked:
> I'd like to hear the opinion of Cogito users about renaming the Cogito
> commands accordingly to the GIT big renames. This would be:
>
> cg-pull -> cg-fetch
> cg-update -> cg-pull
It took me a good long while of confusion before I
realized that cg and git were inconsistent in their
command names and meanings here. It was the source
of Head Scratching and Not Understanding.
I am firmly of the opinion that CG should either rename
these commands to be more consistent with GIT, or else
make up totally new, different names unrelated to git
entirely. The reuse of "pull" alone will be, IMO, a
constant source of documentation and explanation headaches.
As with git, sooner rather than later, please.
jdl
next prev parent reply other threads:[~2005-09-16 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 23:46 Should Cogito scripts be renamed? Petr Baudis
2005-09-16 0:07 ` jdl [this message]
2005-09-16 15:40 ` Josef Weidendorfer
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=E1EG3ku-0005hU-Eb@jdl.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.org \
/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).