From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Avoiding the three-windows merging with Git
Date: Wed, 27 Nov 2019 20:45:26 +0100 [thread overview]
Message-ID: <87fti99k89.fsf@gmail.com> (raw)
In-Reply-To: <83eextqq55.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Nov 2019 17:45:42 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Richard Stallman <rms@gnu.org>
>> Cc: eliz@gnu.org, emacs-devel@gnu.org
>> Date: Wed, 27 Nov 2019 01:45:50 -0500
>>
>> Does it operate purely locally? No connection to any remote site?
>
> Yes, it arranges for the upstream repository to be on your local
> machine, just in another directory.
Right. Git commands that interact with remote repositories work just as
well with local copies of a repository. It's not something I've seen
used much, but I find it useful for messing ar^W^Weducative purposes.
That's why I put quotes around "central repository"; nothing actually
leaves the machine the script runs on. The server-hosted-repo folder
(whose name might be confusing; I should have simply called it
"upstream-repo") is only "central" insofar as the other two repositories
are set up to synchronize with it when running vc-update and vc-push.
prev parent reply other threads:[~2019-11-27 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 3:14 Avoiding the three-windows merging with Git Richard Stallman
2019-11-25 3:32 ` Eli Zaretskii
2019-11-26 3:46 ` Richard Stallman
2019-11-26 7:16 ` Kévin Le Gouguec
2019-11-27 6:45 ` Richard Stallman
2019-11-27 9:39 ` Marcin Borkowski
2019-11-27 20:15 ` Kévin Le Gouguec
2019-11-27 22:48 ` Marcin Borkowski
2019-11-28 4:17 ` Richard Stallman
2019-11-27 15:45 ` Eli Zaretskii
2019-11-27 19:45 ` Kévin Le Gouguec [this message]
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=87fti99k89.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).