From: "Steven Walter" <stevenrwalter@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"Elijah Newren" <newren@gmail.com>,
"Govind Salinas" <govind@sophiasuchtig.com>,
git@vger.kernel.org
Subject: Re: Revert behavior [Was: Re: [ANNOUNCE] yap: Yet Another (Git) Porcelain]
Date: Tue, 9 Sep 2008 17:39:46 -0400 [thread overview]
Message-ID: <e06498070809091439q1c543807pd6e74b7ada32434@mail.gmail.com> (raw)
In-Reply-To: <20080909212834.GC10544@machine.or.cz>
On Tue, Sep 9, 2008 at 5:28 PM, Petr Baudis <pasky@suse.cz> wrote:
> On Tue, Sep 09, 2008 at 03:38:13PM +0200, Jakub Narebski wrote:
>> By the way, I think the fact that in different SCMs meaning of
>> "$scm revert" and of "$scm reset" differs widely caused Mercurial
>> to adopt "hg backout" for creating a commit which reverts changes
>> (cherry-pick -R), and "hg rollback" to undo last commit.
>
> This brings up a point I wanted to raise - sometimes when the meanings
> across the systems (including Git) are too conflicting, it should be
> considered to use a completely different command name whatsoever to
> reduce the confusion. This is e.g. the reason Cogito had no "pull"
> (but "update") or "checkout" (but "restore" and "switch") commands.
I agree with this. That's part of the problem I have with schemes to
make commands work similarly to other SCMs. If you give, for example,
eg a mode to act like "svn revert;" that all well and good until the
user runs "git diff" and you're made a liar. In svn, there would be
no diff, because the files all match their respective upstream
versions. In git, you would see changes because the file no longer
matches the last commit.
It it a delicate balance to have the user interface match both the
mental model of the user and the storage model of the tool. That's
what all of these projects, (git, cogito, yap, eg, pyrite) are
attempting to do. I don't know of an objective way to measure success
in this attempt, other than simple popularity. Popularity suggests
that the git porcelain is the most successful, and I would agree
regarding storage model, but I am not convinced that it best matches a
typical SCM user's mental model.
--
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
-Robert Heinlein
next prev parent reply other threads:[~2008-09-09 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 13:26 Revert behavior [Was: Re: [ANNOUNCE] yap: Yet Another (Git) Porcelain] Elijah Newren
2008-09-09 13:38 ` Jakub Narebski
2008-09-09 16:37 ` Govind Salinas
2008-09-09 17:29 ` Steven Walter
2008-09-09 20:19 ` Elijah Newren
2008-09-09 21:50 ` Steven Walter
2008-09-09 23:02 ` Elijah Newren
2008-09-09 20:20 ` Elijah Newren
2008-09-09 21:28 ` Petr Baudis
2008-09-09 21:39 ` Steven Walter [this message]
2008-09-09 22:10 ` Revert behavior Junio C Hamano
2008-09-09 22:30 ` Steven Walter
2008-09-09 22:51 ` Elijah Newren
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=e06498070809091439q1c543807pd6e74b7ada32434@mail.gmail.com \
--to=stevenrwalter@gmail.com \
--cc=git@vger.kernel.org \
--cc=govind@sophiasuchtig.com \
--cc=jnareb@gmail.com \
--cc=newren@gmail.com \
--cc=pasky@suse.cz \
/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).