unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Magit
Date: Sun, 04 Sep 2022 08:25:54 +0300	[thread overview]
Message-ID: <8335d7n21p.fsf@gnu.org> (raw)
In-Reply-To: <87edwrzsea.fsf@gmail.com> (message from Payas Relekar on Sun, 04 Sep 2022 09:43:11 +0530)

> From: Payas Relekar <relekarpayas@gmail.com>
> Date: Sun, 04 Sep 2022 09:43:11 +0530
> 
> Akib Azmain Turja <akib@disroot.org> writes:
> 
> >>> What about VC?  Why people don't use it much?
> >>
> >> People do use VC quite a lot.
> >
> > Maybe my wordings were not clear.  I meant - why people don't talk about
> > VC much?
> 
> VC is alright, but it requires some basic learning.

It is fully described in the Emacs manual.

If you need to work with several different VCSes, VC is a better
alternative, as it strives to present a unified UI for all the VCSes
it supports, from the now ancient RCS, via CVS and Subversion, all the
way to Git and Mercurial.

> Magit is instantly intuitive and all interactive. Its a difference
> between telling computer what to do vs computer asking/presenting
> options for what needs to be done.
> 
> Its bit hard to describe, but in short Magit provides superior UX by a
> wide margin.

Magit has a very different, unique UI that could be more convenient to
some/many people who want to use only Git.  Which is why we want it to
be part of the Emacs core.



  reply	other threads:[~2022-09-04  5:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04  4:13 Magit Payas Relekar
2022-09-04  5:25 ` Eli Zaretskii [this message]
2022-09-04  5:51   ` Magit tomas
  -- strict thread matches above, loose matches on Subject: below --
2022-09-03 14:35 Magit Payas Relekar
2022-08-31  5:41 Hunting the culprit package Pankaj Jangid
2022-08-31 12:25 ` Stefan Monnier
2022-08-31 17:20   ` Pankaj Jangid
2022-08-31 22:12     ` Stefan Monnier
2022-09-01  0:31       ` T.V Raman
2022-09-03  2:51         ` Magit Richard Stallman
2022-09-03  6:29           ` Magit Akib Azmain Turja
2022-09-03 14:20             ` Magit Stefan Monnier
2022-09-03 14:56               ` Magit Eli Zaretskii
2022-09-03 18:22                 ` Magit Akib Azmain Turja
2022-09-03 18:34                   ` Magit Eli Zaretskii
2022-09-04  2:47                     ` Magit Akib Azmain Turja
2022-09-04  5:16                       ` Magit Eli Zaretskii
2022-09-03 15:16               ` Magit Stefan Kangas
2022-09-03 18:32                 ` Magit Akib Azmain Turja
2022-09-03 19:09                   ` Magit Philip Kaludercic
2022-09-05  4:03                     ` Magit Richard Stallman
2022-09-05  8:58                       ` Magit Philip Kaludercic
2022-09-07  2:19                         ` Magit Richard Stallman
2022-09-07  3:33                           ` Magit Phil Sainty
2022-09-07 12:40                           ` Magit Stefan Monnier
2022-09-07 13:02                             ` Magit Akib Azmain Turja
2022-09-03 18:45                 ` Magit Stefan Monnier
2022-09-05  4:03             ` Magit Richard Stallman
2022-09-05  9:04               ` Magit Philip Kaludercic
2022-09-05 11:48                 ` Magit Eli Zaretskii
2022-09-07  2:19                 ` Magit Richard Stallman

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8335d7n21p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=relekarpayas@gmail.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://git.savannah.gnu.org/cgit/emacs.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).