From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk
Date: Tue, 02 Feb 2021 17:06:52 +0200 [thread overview]
Message-ID: <83lfc65x0z.fsf@gnu.org> (raw)
In-Reply-To: <87ft2evq8b.fsf@igel.home> (message from Andreas Schwab on Tue, 02 Feb 2021 09:16:52 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Tue, 02 Feb 2021 09:16:52 +0100
> Cc: yamaoka@jpl.org, Stefan Monnier <monnier@iro.umontreal.ca>,
> emacs-devel@gnu.org
>
> On Feb 02 2021, Richard Stallman wrote:
>
> > Would someone please tell me what "remote tracking" means, concretely?
>
> See gitglossary(7).
Which divulges this:
remote-tracking branch
A "ref" that is used to follow changes from another
"repository". It typically looks like refs/remotes/foo/bar
(indicating that it tracks a branch named bar in a remote named
foo), and matches the right-hand-side of a configured fetch
"refspec". A remote-tracking branch should not contain direct
modifications or have local commits made to it.
Basically, "remote-tracking branch is a branch that tracks some
remote". Very clear, right?
And if you think that the references clarify this, then here they are:
ref
A name that begins with refs/ (e.g. refs/heads/master) that points
to an object name or another ref (the latter is called a symbolic
ref). For convenience, a ref can sometimes be abbreviated when used
as an argument to a Git command; see gitrevisions(7) for
details. Refs are stored in the repository.
refspec
A "refspec" is used by fetch and push to describe the mapping
between remote ref and local ref.
next prev parent reply other threads:[~2021-02-02 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210131223952.429.10439@vcs0.savannah.gnu.org>
[not found] ` <20210131223954.A429420DF3@vcs0.savannah.gnu.org>
2021-02-02 0:44 ` master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk Katsumi Yamaoka
2021-02-02 2:58 ` Stefan Monnier
2021-02-02 5:41 ` Richard Stallman
2021-02-02 6:38 ` Tassilo Horn
2021-02-02 9:06 ` tomas
2021-02-02 15:23 ` Eli Zaretskii
2021-02-02 16:01 ` tomas
2021-02-02 16:21 ` Eli Zaretskii
2021-02-02 16:34 ` git things [was: master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk] tomas
2021-02-03 5:51 ` master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk Richard Stallman
2021-02-02 8:16 ` Andreas Schwab
2021-02-02 15:06 ` Eli Zaretskii [this message]
2021-02-03 5:52 ` Richard Stallman
2021-02-03 14:32 ` Eli Zaretskii
2021-02-04 5:47 ` Richard Stallman
2021-02-02 9:05 ` Lars Ingebrigtsen
2021-02-02 14:43 ` Stefan Monnier
2021-02-02 14:53 ` Lars Ingebrigtsen
2021-02-02 22:12 ` Katsumi Yamaoka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lfc65x0z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.