From: uzibalqa <uzibalqa@proton.me>
To: Po Lu <luangruo@yahoo.com>
Cc: uzibalqa via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Source code, git and cvs
Date: Thu, 20 Jul 2023 13:58:25 +0000 [thread overview]
Message-ID: <6HUp-C43ybkt5vDEYSO5olPY5eqIK3Xw5Kn6E4DSc3HFUj3bLOIE11VaP9iyglyC-jiQ7nIW4h4SFV58-fNOGZfGRRgc_SyYSscsdSfhLlw=@proton.me> (raw)
In-Reply-To: <87v8ee4sad.fsf@yahoo.com>
------- Original Message -------
On Friday, July 21st, 2023 at 1:38 AM, Po Lu <luangruo@yahoo.com> wrote:
> uzibalqa uzibalqa@proton.me writes:
>
> > What is the difference between
> >
> > git clone https://git.savannah.gnu.org/git/emacs.git
> >
> > and
> >
> > git clone -b master git://git.sv.gnu.org/emacs.git
>
>
> The first command checks out the master branch of the Emacs repository
> over the HTTP protocol, while the other does so over the Git protocol.
>
> git.sv.gnu.org/emacs.git means exactly the same as
> git.savannah.gnu.org/git/emacs.git; it is simply a more concise version
> of the other repository path.
>
> The difference between the two paths is of no relevance to prospective
> Emacs developers. All of this is spelt out clearly in CONTRIBUTE and
> countless other documents, such as the manual pages for `git clone'.
>
> > And what is this exactly
> >
> > cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:
> > /sources/emacs co emacs
>
>
> This is an obsolete method of obtaining a checkout of the in-development
> Emacs source code.
I wonder why you have INSTALL and INSTALL.REPO
Because if one gets the emacs source, wouldn't they want to build using instructions
from INSTALL.REPO rather than from INSTALL ?
next prev parent reply other threads:[~2023-07-20 13:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:01 Source code, git and cvs uzibalqa
2023-07-20 13:38 ` Po Lu
2023-07-20 13:58 ` uzibalqa [this message]
2023-07-20 14:23 ` Eli Zaretskii
2023-07-20 15:09 ` uzibalqa
2023-07-20 15:34 ` Robert Pluim
2023-07-20 15:36 ` Eli Zaretskii
2023-07-20 15:47 ` uzibalqa
2023-07-20 16:35 ` Eli Zaretskii
2023-07-20 17:33 ` uzibalqa
2023-07-20 18:31 ` Eli Zaretskii
2023-07-20 19:12 ` uzibalqa
2023-07-20 20:10 ` uzibalqa
2023-07-21 5:22 ` Eli Zaretskii
2023-07-21 6:12 ` Po Lu
2023-07-21 10:43 ` uzibalqa
2023-07-21 10:59 ` uzibalqa
2023-07-21 11:18 ` uzibalqa
2023-07-21 12:30 ` Eli Zaretskii
2023-07-21 12:40 ` uzibalqa
2023-07-21 12:51 ` Eli Zaretskii
2023-07-21 4:27 ` tomas
2023-07-21 10:35 ` uzibalqa
2023-07-21 12:12 ` Po Lu
2023-07-21 12:52 ` uzibalqa
2023-07-21 14:20 ` [External] : " Drew Adams
2023-07-21 15:30 ` uzibalqa
2023-07-20 16:05 ` uzibalqa
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='6HUp-C43ybkt5vDEYSO5olPY5eqIK3Xw5Kn6E4DSc3HFUj3bLOIE11VaP9iyglyC-jiQ7nIW4h4SFV58-fNOGZfGRRgc_SyYSscsdSfhLlw=@proton.me' \
--to=uzibalqa@proton.me \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.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.
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).