unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Omar Polo <op@omarpolo.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
	timo.myyra@bittivirhe.fi, emacs-devel@gnu.org
Subject: Re: [elpa] New package: vc-got
Date: Tue, 31 Aug 2021 16:00:50 +0200	[thread overview]
Message-ID: <87bl5dy9r8.fsf@omarpolo.com> (raw)
In-Reply-To: <ab1efc26-817a-49f6-e32a-109fbda2e18f@yandex.ru>


Dmitry Gutov <dgutov@yandex.ru> writes:

> On 31.08.2021 16:10, Eli Zaretskii wrote:
>> What do people think about the need to have Got support in Emacs OOTB?
>> Is it important enough to have it in core?

I don't think; while I really like using got and developing vc-got as
part of emacs itself would simplify some aspects for me (there were some
changes in VC between emacs 27.2 and the current master), it's not that
widespread to justify moving into core IMHO.

All the code was written by people with a copyright assignment, and I'll
ensure that this will hold true in the future, so if it becomes really
popular we can always move it to core later, right?

> It's an alternative client for Git repositories, right?
>
> We already have vc-git.

Yes and no.  got uses the git format for *bare repositories* and in this
sense it's always possible to switch back and forth from got and git and
collaborate with other peoples.  (in fact I'm using it to track the
emacs repo on my machine).  But Got it's not a Git porcelain, it is
another VCS that happens to use the same format for storing
commits/tags/branches.



  parent reply	other threads:[~2021-08-31 14:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 10:17 [elpa] New package: vc-got Omar Polo
2021-08-31 13:10 ` Eli Zaretskii
2021-08-31 13:31   ` Dmitry Gutov
2021-08-31 13:41     ` Eli Zaretskii
2021-08-31 13:46       ` Dmitry Gutov
2021-08-31 13:47         ` Eli Zaretskii
2021-08-31 13:55           ` Dmitry Gutov
2021-08-31 14:00             ` Eli Zaretskii
2021-08-31 14:02               ` Dmitry Gutov
2021-08-31 14:07                 ` Eli Zaretskii
2021-08-31 14:08                 ` Eli Zaretskii
2021-08-31 14:21                   ` Stefan Kangas
2021-08-31 15:37                     ` Eli Zaretskii
2021-10-17  4:57               ` Jean Louis
2021-10-17  6:21                 ` Eli Zaretskii
2021-10-17  7:33                   ` Jean Louis
2021-10-17 10:02                     ` Eli Zaretskii
2021-10-17 10:13                     ` Omar Polo
2021-08-31 14:00     ` Omar Polo [this message]
2021-08-31 14:34       ` Dmitry Gutov
2021-08-31 14:38         ` Omar Polo
2021-08-31 15:38       ` Eli Zaretskii
2021-08-31 14:44   ` Dmitry Gutov
2021-08-31 15:40     ` Eli Zaretskii
2021-08-31 13:32 ` Philip Kaludercic
2021-08-31 13:59   ` Omar Polo
2021-08-31 16:54     ` Philip Kaludercic
2021-09-09 15:50     ` Philip Kaludercic

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=87bl5dy9r8.fsf@omarpolo.com \
    --to=op@omarpolo.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=timo.myyra@bittivirhe.fi \
    /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).