From: Lars Magne Ingebrigtsen <lmi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: vc for git users.
Date: Tue, 29 Oct 2019 14:59:28 +0100 [thread overview]
Message-ID: <87sgnbzm7z.fsf@gnus.org> (raw)
In-Reply-To: <mailman.65.1572356923.4165.help-gnu-emacs@gnu.org> (Eli Zaretskii's message of "Tue, 29 Oct 2019 15:48:34 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Bottom line, I don't understand the specifics of the complaint.
I tried explaining Emacs' git support through vc was the other day, and
he just couldn't wrap his head around how easy Emacs makes it. "But...
but... staging... the index... how... wha..." When you're finally
proficient in a nigh-incomprehensible tool like command line git, it
sounds as if something's missing in Emacs somehow.
So I think it might make some sense to write some text that explains
that, indeed, `C-x v v' makes most of that just go away -- you don't
have to think explicitly in those git terms. And `M-x vc-dir' takes
care of the rest.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-29 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 14:21 vc for git users Ergus
2019-10-28 15:36 ` Pankaj Jangid
2019-10-28 16:16 ` Eli Zaretskii
2019-10-28 21:50 ` Skip Montanaro
2019-10-28 23:40 ` VanL
2019-10-29 8:30 ` Eric S Fraga
2019-10-29 2:42 ` Ergus via Users list for the GNU Emacs text editor
2019-10-29 13:48 ` Eli Zaretskii
[not found] ` <mailman.65.1572356923.4165.help-gnu-emacs@gnu.org>
2019-10-29 13:59 ` Lars Magne Ingebrigtsen [this message]
2019-10-29 14:18 ` Eli Zaretskii
2019-10-29 15:31 ` Dmitry Gutov
2019-10-29 16:31 ` Eli Zaretskii
2019-10-29 17:38 ` Stefan Monnier
2019-10-29 18:00 ` Steinar Bang
2019-10-29 20:09 ` Štěpán Němec
2019-10-30 9:34 ` Marcin Borkowski
2019-10-30 13:43 ` Robert Pluim
[not found] ` <mailman.69.1572358708.4165.help-gnu-emacs@gnu.org>
2019-10-29 20:52 ` Lars Magne Ingebrigtsen
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=87sgnbzm7z.fsf@gnus.org \
--to=lmi@gnus.org \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.