2007-01-09 12:28:51 +08:00
|
|
|
git-remote(1)
|
2015-10-23 01:09:07 +08:00
|
|
|
=============
|
2007-01-09 12:28:51 +08:00
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2014-02-09 04:41:35 +08:00
|
|
|
git-remote - Manage set of tracked repositories
|
2007-01-09 12:28:51 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
|
|
|
|
[verse]
|
2008-06-30 14:09:04 +08:00
|
|
|
'git remote' [-v | --verbose]
|
2021-11-07 02:48:55 +08:00
|
|
|
'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=(fetch|push)] <name> <URL>
|
builtin/remote.c: show progress when renaming remote references
When renaming a remote, Git needs to rename all remote tracking
references to the remote's new name (e.g., renaming
"refs/remotes/old/foo" to "refs/remotes/new/foo" when renaming a remote
from "old" to "new").
This can be somewhat slow when there are many references to rename,
since each rename is done in a separate call to rename_ref() as opposed
to grouping all renames together into the same transaction. It would be
nice to execute all renames as a single transaction, but there is a
snag: the reference transaction backend doesn't support renames during a
transaction (only individually, via rename_ref()).
The reasons there are described in more detail in [1], but the main
problem is that in order to preserve the existing reflog, it must be
moved while holding both locks (i.e., on "oldname" and "newname"), and
the ref transaction code doesn't support inserting arbitrary actions
into the middle of a transaction like that.
As an aside, adding support for this to the ref transaction code is
less straightforward than inserting both a ref_update() and ref_delete()
call into the same transaction. rename_ref()'s special handling to
detect D/F conflicts would need to be rewritten for the transaction code
if we wanted to proactively catch D/F conflicts when renaming a
reference during a transaction. The reftable backend could support this
much more readily because of its lack of D/F conflicts.
Instead of a more complex modification to the ref transaction code,
display a progress meter when running verbosely in order to convince the
user that Git is doing work while renaming a remote.
This is mostly done as-expected, with the minor caveat that we
intentionally count symrefs renames twice, since renaming a symref takes
place over two separate calls (one to delete the old one, and another to
create the new one).
[1]: https://lore.kernel.org/git/572367B4.4050207@alum.mit.edu/
Suggested-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-03-04 06:25:18 +08:00
|
|
|
'git remote rename' [--[no-]progress] <old> <new>
|
2012-09-06 20:25:23 +08:00
|
|
|
'git remote remove' <name>
|
2013-09-21 23:51:45 +08:00
|
|
|
'git remote set-head' <name> (-a | --auto | -d | --delete | <branch>)
|
2012-02-18 19:17:47 +08:00
|
|
|
'git remote set-branches' [--add] <name> <branch>...
|
2015-09-16 09:53:47 +08:00
|
|
|
'git remote get-url' [--push] [--all] <name>
|
2010-01-19 01:18:02 +08:00
|
|
|
'git remote set-url' [--push] <name> <newurl> [<oldurl>]
|
|
|
|
|
'git remote set-url --add' [--push] <name> <newurl>
|
2021-11-07 02:48:55 +08:00
|
|
|
'git remote set-url --delete' [--push] <name> <URL>
|
2013-04-24 21:54:37 +08:00
|
|
|
'git remote' [-v | --verbose] 'show' [-n] <name>...
|
|
|
|
|
'git remote prune' [-n | --dry-run] <name>...
|
2010-10-09 01:31:17 +08:00
|
|
|
'git remote' [-v | --verbose] 'update' [-p | --prune] [(<group> | <remote>)...]
|
2007-01-09 12:28:51 +08:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
Manage the set of repositories ("remotes") whose branches you track.
|
|
|
|
|
|
|
|
|
|
|
2008-06-08 09:36:10 +08:00
|
|
|
OPTIONS
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
-v::
|
|
|
|
|
--verbose::
|
|
|
|
|
Be a little more verbose and show remote url after name.
|
2020-10-09 04:23:56 +08:00
|
|
|
NOTE: This must be placed between `remote` and subcommand.
|
2008-06-08 09:36:10 +08:00
|
|
|
|
|
|
|
|
|
2007-02-04 12:02:59 +08:00
|
|
|
COMMANDS
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
With no arguments, shows a list of existing remotes. Several
|
|
|
|
|
subcommands are available to perform operations on the remotes.
|
|
|
|
|
|
|
|
|
|
'add'::
|
|
|
|
|
|
2020-10-09 04:23:56 +08:00
|
|
|
Add a remote named <name> for the repository at
|
2021-11-07 02:48:55 +08:00
|
|
|
<URL>. The command `git fetch <name>` can then be used to create and
|
2007-01-09 12:28:51 +08:00
|
|
|
update remote-tracking branches <name>/<branch>.
|
2007-02-26 15:26:11 +08:00
|
|
|
+
|
|
|
|
|
With `-f` option, `git fetch <name>` is run immediately after
|
|
|
|
|
the remote information is set up.
|
|
|
|
|
+
|
2010-04-20 07:31:31 +08:00
|
|
|
With `--tags` option, `git fetch <name>` imports every tag from the
|
|
|
|
|
remote repository.
|
|
|
|
|
+
|
|
|
|
|
With `--no-tags` option, `git fetch <name>` does not import tags from
|
|
|
|
|
the remote repository.
|
|
|
|
|
+
|
2015-03-02 21:08:09 +08:00
|
|
|
By default, only tags on fetched branches are imported
|
|
|
|
|
(see linkgit:git-fetch[1]).
|
|
|
|
|
+
|
2007-02-26 15:26:11 +08:00
|
|
|
With `-t <branch>` option, instead of the default glob
|
|
|
|
|
refspec for the remote to track all branches under
|
2011-06-23 23:33:05 +08:00
|
|
|
the `refs/remotes/<name>/` namespace, a refspec to track only `<branch>`
|
2007-02-26 15:26:11 +08:00
|
|
|
is created. You can give more than one `-t <branch>` to track
|
2007-05-06 02:23:12 +08:00
|
|
|
multiple branches without grabbing all branches.
|
2007-02-26 15:26:11 +08:00
|
|
|
+
|
2011-06-23 23:33:05 +08:00
|
|
|
With `-m <master>` option, a symbolic-ref `refs/remotes/<name>/HEAD` is set
|
2009-02-25 16:32:25 +08:00
|
|
|
up to point at remote's `<master>` branch. See also the set-head command.
|
2007-09-03 04:10:14 +08:00
|
|
|
+
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
When a fetch mirror is created with `--mirror=fetch`, the refs will not
|
remote: separate the concept of push and fetch mirrors
git-remote currently has one option, "--mirror", which sets
up mirror configuration which can be used for either
fetching or pushing. It looks like this:
[remote "mirror"]
url = wherever
fetch = +refs/*:refs/*
mirror = true
However, a remote like this can be dangerous and confusing.
Specifically:
1. If you issue the wrong command, it can be devastating.
You are not likely to "push" when you meant to "fetch",
but "git remote update" will try to fetch it, even if
you intended the remote only for pushing. In either
case, the results can be quite destructive. An
unintended push will overwrite or delete remote refs,
and an unintended fetch can overwrite local branches.
2. The tracking setup code can produce confusing results.
The fetch refspec above means that "git checkout -b new
master" will consider refs/heads/master to come from
the remote "mirror", even if you only ever intend to
push to the mirror. It will set up the "new" branch to
track mirror's refs/heads/master.
3. The push code tries to opportunistically update
tracking branches. If you "git push mirror foo:bar",
it will see that we are updating mirror's
refs/heads/bar, which corresponds to our local
refs/heads/bar, and will update our local branch.
To solve this, we split the concept into "push mirrors" and
"fetch mirrors". Push mirrors set only remote.*.mirror,
solving (2) and (3), and making an accidental fetch write
only into FETCH_HEAD. Fetch mirrors set only the fetch
refspec, meaning an accidental push will not force-overwrite
or delete refs on the remote end.
The new syntax is "--mirror=<fetch|push>". For
compatibility, we keep "--mirror" as-is, setting up both
types simultaneously.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-03-31 03:53:19 +08:00
|
|
|
be stored in the 'refs/remotes/' namespace, but rather everything in
|
|
|
|
|
'refs/' on the remote will be directly mirrored into 'refs/' in the
|
|
|
|
|
local repository. This option only makes sense in bare repositories,
|
|
|
|
|
because a fetch would overwrite any local commits.
|
|
|
|
|
+
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
When a push mirror is created with `--mirror=push`, then `git push`
|
|
|
|
|
will always behave as if `--mirror` was passed.
|
2007-01-09 12:28:51 +08:00
|
|
|
|
2008-11-04 02:26:18 +08:00
|
|
|
'rename'::
|
|
|
|
|
|
2010-11-02 23:31:20 +08:00
|
|
|
Rename the remote named <old> to <new>. All remote-tracking branches and
|
2008-11-04 02:26:18 +08:00
|
|
|
configuration settings for the remote are updated.
|
2008-11-11 04:43:03 +08:00
|
|
|
+
|
|
|
|
|
In case <old> and <new> are the same, and <old> is a file under
|
|
|
|
|
`$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to
|
|
|
|
|
the configuration file format.
|
2008-11-04 02:26:18 +08:00
|
|
|
|
2012-09-06 20:25:23 +08:00
|
|
|
'remove'::
|
2007-07-07 23:22:43 +08:00
|
|
|
'rm'::
|
|
|
|
|
|
2010-11-02 23:31:20 +08:00
|
|
|
Remove the remote named <name>. All remote-tracking branches and
|
2007-07-07 23:22:43 +08:00
|
|
|
configuration settings for the remote are removed.
|
|
|
|
|
|
2009-02-25 16:32:25 +08:00
|
|
|
'set-head'::
|
|
|
|
|
|
2011-06-23 23:33:05 +08:00
|
|
|
Sets or deletes the default branch (i.e. the target of the
|
|
|
|
|
symbolic-ref `refs/remotes/<name>/HEAD`) for
|
2009-02-25 16:32:25 +08:00
|
|
|
the named remote. Having a default branch for a remote is not required,
|
|
|
|
|
but allows the name of the remote to be specified in lieu of a specific
|
|
|
|
|
branch. For example, if the default branch for `origin` is set to
|
|
|
|
|
`master`, then `origin` may be specified wherever you would normally
|
|
|
|
|
specify `origin/master`.
|
|
|
|
|
+
|
2013-09-21 23:51:45 +08:00
|
|
|
With `-d` or `--delete`, the symbolic ref `refs/remotes/<name>/HEAD` is deleted.
|
2009-02-25 16:32:25 +08:00
|
|
|
+
|
2013-09-21 23:51:45 +08:00
|
|
|
With `-a` or `--auto`, the remote is queried to determine its `HEAD`, then the
|
2011-06-23 23:33:05 +08:00
|
|
|
symbolic-ref `refs/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote
|
2020-10-09 04:23:56 +08:00
|
|
|
`HEAD` is pointed at `next`, `git remote set-head origin -a` will set
|
2011-06-23 23:33:05 +08:00
|
|
|
the symbolic-ref `refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will
|
2009-02-25 16:32:25 +08:00
|
|
|
only work if `refs/remotes/origin/next` already exists; if not it must be
|
|
|
|
|
fetched first.
|
|
|
|
|
+
|
2020-10-09 04:23:56 +08:00
|
|
|
Use `<branch>` to set the symbolic-ref `refs/remotes/<name>/HEAD` explicitly. e.g., `git
|
|
|
|
|
remote set-head origin master` will set the symbolic-ref `refs/remotes/origin/HEAD` to
|
2009-02-25 16:32:25 +08:00
|
|
|
`refs/remotes/origin/master`. This will only work if
|
|
|
|
|
`refs/remotes/origin/master` already exists; if not it must be fetched first.
|
|
|
|
|
+
|
|
|
|
|
|
2010-05-20 02:38:50 +08:00
|
|
|
'set-branches'::
|
|
|
|
|
|
|
|
|
|
Changes the list of branches tracked by the named remote.
|
|
|
|
|
This can be used to track a subset of the available remote branches
|
|
|
|
|
after the initial setup for a remote.
|
|
|
|
|
+
|
|
|
|
|
The named branches will be interpreted as if specified with the
|
2020-10-09 04:23:56 +08:00
|
|
|
`-t` option on the `git remote add` command line.
|
2010-05-20 02:38:50 +08:00
|
|
|
+
|
|
|
|
|
With `--add`, instead of replacing the list of currently tracked
|
|
|
|
|
branches, adds to that list.
|
|
|
|
|
|
2015-09-16 09:53:47 +08:00
|
|
|
'get-url'::
|
|
|
|
|
|
|
|
|
|
Retrieves the URLs for a remote. Configurations for `insteadOf` and
|
|
|
|
|
`pushInsteadOf` are expanded here. By default, only the first URL is listed.
|
|
|
|
|
+
|
2016-06-28 19:40:11 +08:00
|
|
|
With `--push`, push URLs are queried rather than fetch URLs.
|
2015-09-16 09:53:47 +08:00
|
|
|
+
|
2016-06-28 19:40:11 +08:00
|
|
|
With `--all`, all URLs for the remote will be listed.
|
2015-09-16 09:53:47 +08:00
|
|
|
|
2010-01-19 01:18:02 +08:00
|
|
|
'set-url'::
|
|
|
|
|
|
2015-01-30 04:26:09 +08:00
|
|
|
Changes URLs for the remote. Sets first URL for remote <name> that matches
|
2010-01-19 01:18:02 +08:00
|
|
|
regex <oldurl> (first URL if no <oldurl> is given) to <newurl>. If
|
2015-01-30 04:26:09 +08:00
|
|
|
<oldurl> doesn't match any URL, an error occurs and nothing is changed.
|
2010-01-19 01:18:02 +08:00
|
|
|
+
|
2016-06-28 19:40:11 +08:00
|
|
|
With `--push`, push URLs are manipulated instead of fetch URLs.
|
2010-01-19 01:18:02 +08:00
|
|
|
+
|
2016-06-28 19:40:11 +08:00
|
|
|
With `--add`, instead of changing existing URLs, new URL is added.
|
2010-01-19 01:18:02 +08:00
|
|
|
+
|
2016-06-28 19:40:11 +08:00
|
|
|
With `--delete`, instead of changing existing URLs, all URLs matching
|
2021-11-07 02:48:55 +08:00
|
|
|
regex <URL> are deleted for remote <name>. Trying to delete all
|
2015-01-30 04:26:09 +08:00
|
|
|
non-push URLs is an error.
|
|
|
|
|
+
|
|
|
|
|
Note that the push URL and the fetch URL, even though they can
|
|
|
|
|
be set differently, must still refer to the same place. What you
|
|
|
|
|
pushed to the push URL should be what you would see if you
|
|
|
|
|
immediately fetched from the fetch URL. If you are trying to
|
|
|
|
|
fetch from one place (e.g. your upstream) and push to another (e.g.
|
|
|
|
|
your publishing repository), use two separate remotes.
|
|
|
|
|
|
2010-01-19 01:18:02 +08:00
|
|
|
|
2007-02-04 12:02:59 +08:00
|
|
|
'show'::
|
2007-01-09 12:28:51 +08:00
|
|
|
|
2007-02-04 12:02:59 +08:00
|
|
|
Gives some information about the remote <name>.
|
2007-06-30 16:56:16 +08:00
|
|
|
+
|
|
|
|
|
With `-n` option, the remote heads are not queried first with
|
|
|
|
|
`git ls-remote <name>`; cached information is used instead.
|
2007-02-04 12:02:59 +08:00
|
|
|
|
|
|
|
|
'prune'::
|
|
|
|
|
|
2018-02-10 04:32:12 +08:00
|
|
|
Deletes stale references associated with <name>. By default, stale
|
|
|
|
|
remote-tracking branches under <name> are deleted, but depending on
|
|
|
|
|
global configuration and the configuration of the remote we might even
|
|
|
|
|
prune local tags that haven't been pushed there. Equivalent to `git
|
|
|
|
|
fetch --prune <name>`, except that no new references will be fetched.
|
|
|
|
|
+
|
|
|
|
|
See the PRUNING section of linkgit:git-fetch[1] for what it'll prune
|
|
|
|
|
depending on various configuration.
|
2007-06-30 16:56:16 +08:00
|
|
|
+
|
2020-10-09 04:23:56 +08:00
|
|
|
With `--dry-run` option, report what branches would be pruned, but do not
|
2008-06-10 22:51:35 +08:00
|
|
|
actually prune them.
|
2007-02-19 12:00:00 +08:00
|
|
|
|
|
|
|
|
'update'::
|
|
|
|
|
|
2018-05-30 23:37:01 +08:00
|
|
|
Fetch updates for remotes or remote groups in the repository as defined by
|
2020-10-09 04:23:56 +08:00
|
|
|
`remotes.<group>`. If neither group nor remote is specified on the command line,
|
2009-08-11 08:52:07 +08:00
|
|
|
the configuration parameter remotes.default will be used; if
|
2007-11-14 02:17:47 +08:00
|
|
|
remotes.default is not defined, all remotes which do not have the
|
2020-10-09 04:23:56 +08:00
|
|
|
configuration parameter `remote.<name>.skipDefaultUpdate` set to true will
|
2007-12-29 14:20:38 +08:00
|
|
|
be updated. (See linkgit:git-config[1]).
|
2009-04-03 17:03:44 +08:00
|
|
|
+
|
2018-02-10 04:32:12 +08:00
|
|
|
With `--prune` option, run pruning against all the remotes that are updated.
|
2007-02-02 13:06:08 +08:00
|
|
|
|
2007-02-04 12:02:59 +08:00
|
|
|
|
|
|
|
|
DISCUSSION
|
|
|
|
|
----------
|
|
|
|
|
|
2007-01-09 12:28:51 +08:00
|
|
|
The remote configuration is achieved using the `remote.origin.url` and
|
|
|
|
|
`remote.origin.fetch` configuration variables. (See
|
2007-12-29 14:20:38 +08:00
|
|
|
linkgit:git-config[1]).
|
2007-01-09 12:28:51 +08:00
|
|
|
|
2020-10-27 17:41:36 +08:00
|
|
|
EXIT STATUS
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
On success, the exit status is `0`.
|
|
|
|
|
|
|
|
|
|
When subcommands such as 'add', 'rename', and 'remove' can't find the
|
|
|
|
|
remote in question, the exit status is `2`. When the remote already
|
|
|
|
|
exists, the exit status is `3`.
|
|
|
|
|
|
|
|
|
|
On any other error, the exit status may be any other non-zero value.
|
|
|
|
|
|
2018-04-30 23:35:33 +08:00
|
|
|
EXAMPLES
|
2007-01-09 12:28:51 +08:00
|
|
|
--------
|
|
|
|
|
|
2007-03-01 06:05:42 +08:00
|
|
|
* Add a new remote, fetch, and check out a branch from it
|
|
|
|
|
+
|
2007-01-09 12:28:51 +08:00
|
|
|
------------
|
|
|
|
|
$ git remote
|
|
|
|
|
origin
|
|
|
|
|
$ git branch -r
|
2013-06-22 22:46:26 +08:00
|
|
|
origin/HEAD -> origin/master
|
|
|
|
|
origin/master
|
|
|
|
|
$ git remote add staging git://git.kernel.org/.../gregkh/staging.git
|
2007-01-09 12:28:51 +08:00
|
|
|
$ git remote
|
|
|
|
|
origin
|
2013-06-22 22:46:26 +08:00
|
|
|
staging
|
|
|
|
|
$ git fetch staging
|
|
|
|
|
...
|
|
|
|
|
From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
|
|
|
|
|
* [new branch] master -> staging/master
|
|
|
|
|
* [new branch] staging-linus -> staging/staging-linus
|
|
|
|
|
* [new branch] staging-next -> staging/staging-next
|
2007-01-09 12:28:51 +08:00
|
|
|
$ git branch -r
|
2013-06-22 22:46:26 +08:00
|
|
|
origin/HEAD -> origin/master
|
|
|
|
|
origin/master
|
|
|
|
|
staging/master
|
|
|
|
|
staging/staging-linus
|
|
|
|
|
staging/staging-next
|
2019-03-29 18:39:19 +08:00
|
|
|
$ git switch -c staging staging/master
|
2007-01-09 12:28:51 +08:00
|
|
|
...
|
|
|
|
|
------------
|
|
|
|
|
|
2010-01-10 07:33:00 +08:00
|
|
|
* Imitate 'git clone' but track only selected branches
|
2007-03-01 06:05:42 +08:00
|
|
|
+
|
|
|
|
|
------------
|
|
|
|
|
$ mkdir project.git
|
|
|
|
|
$ cd project.git
|
|
|
|
|
$ git init
|
|
|
|
|
$ git remote add -f -t master -m master origin git://example.com/git.git/
|
|
|
|
|
$ git merge origin
|
|
|
|
|
------------
|
|
|
|
|
|
|
|
|
|
|
2008-05-29 07:55:27 +08:00
|
|
|
SEE ALSO
|
2007-01-09 12:28:51 +08:00
|
|
|
--------
|
2007-12-29 14:20:38 +08:00
|
|
|
linkgit:git-fetch[1]
|
|
|
|
|
linkgit:git-branch[1]
|
|
|
|
|
linkgit:git-config[1]
|
2007-01-09 12:28:51 +08:00
|
|
|
|
|
|
|
|
GIT
|
|
|
|
|
---
|
2008-06-06 15:07:32 +08:00
|
|
|
Part of the linkgit:git[1] suite
|
