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:38:35 +0200 [thread overview]
Message-ID: <87sfypslvv.fsf@omarpolo.com> (raw)
In-Reply-To: <6ac8ff5c-bf61-0a17-91e3-a1b80322fcb2@yandex.ru>
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 31.08.2021 17:00, Omar Polo wrote:
>> 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?
>
> Yup.
>
>>> 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.
>
> So you don't (and can't) use Git to commit or even init/clone/push?
The two VCS can share the same bare repository, and can push/pull from
the same remote. In this sense, they're interoperable.
The usual workflow is to clone a bare repository (with either `got
clone' or `git clone --bare'), then checkout it into a worktree with
`got checkout' and start working.
If you need to use git for a specific reason, you re-clone the
repository (using git this time) and work with git. Then you can
push/pull your changes etc. But the exact same worktree cannot be
shared between git and got, they use different formats for that.
> But can collaborate with others. It's an interesting tradeoff.
>
> Then yes, the decision should be based on what we know about its popularity.
next prev parent reply other threads:[~2021-08-31 14:38 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
2021-08-31 14:34 ` Dmitry Gutov
2021-08-31 14:38 ` Omar Polo [this message]
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=87sfypslvv.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).