unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: op@omarpolo.com, emacs-devel@gnu.org, timo.myyra@bittivirhe.fi,
	dgutov@yandex.ru
Subject: Re: [elpa] New package: vc-got
Date: Sun, 17 Oct 2021 10:33:39 +0300	[thread overview]
Message-ID: <YWvR01m47fEIkKP9@protected.localdomain> (raw)
In-Reply-To: <835ytwgoj7.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2021-10-17 09:21]:
> > Date: Sun, 17 Oct 2021 07:57:42 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: Dmitry Gutov <dgutov@yandex.ru>, timo.myyra@bittivirhe.fi,
> >   op@omarpolo.com, emacs-devel@gnu.org
> > 
> > * Eli Zaretskii <eliz@gnu.org> [2021-08-31 17:06]:
> > > How about keeping it out of vc-handled-backends, so that people who
> > > want could replace Git with Got?
> > 
> > Git and Got are different VCS systems. Once can understand its
> > goals by reading the reference:
> 
> Is that an agreement with my proposal, or its contradiction?  And in
> any case, what is the rationale?

It is just remark on differences. I don't think that people would
replace Git with Got as how I see it, Got is not replacement for
Git. It is VCS in its own. I think Got and Git could be both in
vc-handled-backends if user wants it so.



Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  reply	other threads:[~2021-10-17  7:33 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 [this message]
2021-10-17 10:02                     ` Eli Zaretskii
2021-10-17 10:13                     ` Omar Polo
2021-08-31 14:00     ` Omar Polo
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=YWvR01m47fEIkKP9@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=op@omarpolo.com \
    --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).