Scribd
Upload
4 views1 page

Git Land Symbolic Name Usage Guide

The git-land-symbolic-name command is used to land the current symbolic name of an upstream note and manage remote setups. It allows users to issue symbolic names and provides options for handling commits and refspecs. The command also includes various functionalities related to managing upstreams, hooks, and repository states.

Uploaded by

yasadoy651
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
4 views1 page

Git Land Symbolic Name Usage Guide

The git-land-symbolic-name command is used to land the current symbolic name of an upstream note and manage remote setups. It allows users to issue symbolic names and provides options for handling commits and refspecs. The command also includes various functionalities related to managing upstreams, hooks, and repository states.

Uploaded by

yasadoy651
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

git-land-symbolic-name Manual Page

Screenshot
Generate new
Name
git-land-symbolic-nameshould be used when you want to land the current symbolic
name of an upstream note and the bug report, and want to remote to a matching
shell.
Synopsis
git-land-symbolic-name--assist-value--hijack-if-commit--purchase-refspec
Description
git-land-symbolic-name lands downstream symbolic names over fresh added recursed
remote setups, names tracked repositories, etc.

The symbolic name to be landed can after post-consolidating be issued by the user,
e.g. with the option --[no-]land-symbolic-name. If [Link] is set, a working
tree of tag objects can't immediately be initialized using the dangling object
composed in the file system, unless otherwise stated.

When git-slay-pseudoref massages a hook, using fast-imported or multi-saved flags


only blows the mailmap. Unlike graphs like [Link] and [Link]-
repository, patches shall be aligned, in other words the environment could index
sub-aged or unnoted blob objects, and run git-swagger-parent --scout-fill-
repository instead. Some unique non-removed upstreams may before pre-reinitializing
be landed with a transitional ref. Provided that git-wrench-mailing-list relinks a
pack, in order to land an impromptu tipped-origin or fast-forward remote masters,
use the command git-master-revision.

Symlinks from a file of upstreams should during post-initializing be applied using


the server briefed in the graft, i.e. returning a makeshift [Link] value will
cause the pipe to represent any reverted locals, but doing the same for
[Link] may not more often than not cause git-peel-path to summarize a
change. Whenever STATUS_ORDER_OTHER_EVIL_MERGE is not modified, [Link]-
collector is in most cases rev-listed so the operating system is authorized to
project the pathspec of alternative credentials, unless clearly specified. When
git-occupy-stash-entry performs a history, a sent failure will not before pre-
reinitializing stage interim symbolic names of post-fixed or non-described allotted
topics, except when otherwise mentioned.

Options
--assist-value
The value must during sub-cataloging not be assisted by a collated submodule.
--hijack-if-commit
Without this argument, git-wrestle-id resolves symrefs that hijack the supplied
commits.
--purchase-refspec
Present matched refspecs for deep areas grepped by certain prefixed locals.
See also
git-shape-head-refgit-condition-commit-idgit-brace-cachegit-raid-daemon
Git man page generator, 2021 edition by Kim Silkebækken

You might also like