2009-10-22 19:25:20 +00:00
|
|
|
--commit::
|
|
|
|
|
--no-commit::
|
|
|
|
|
Perform the merge and commit the result. This option can
|
|
|
|
|
be used to override --no-commit.
|
|
|
|
|
+
|
|
|
|
|
With --no-commit perform the merge but pretend the merge
|
|
|
|
|
failed and do not autocommit, to give the user a chance to
|
|
|
|
|
inspect and further tweak the merge result before committing.
|
2005-11-07 05:30:56 +00:00
|
|
|
|
2011-10-08 18:39:52 +00:00
|
|
|
--edit::
|
2012-03-20 22:39:10 +00:00
|
|
|
--no-edit::
|
2011-10-08 18:39:52 +00:00
|
|
|
Invoke editor before committing successful merge to further
|
2012-03-20 22:39:10 +00:00
|
|
|
edit the default merge message. The `--no-edit` option can be
|
|
|
|
|
used to accept the auto-generated message (this is generally
|
|
|
|
|
discouraged) when merging an annotated tag, in which case
|
|
|
|
|
`git merge` automatically spawns the editor so that the result
|
|
|
|
|
of the GPG verification of the tag can be seen.
|
|
|
|
|
+
|
|
|
|
|
Older scripts may depend on the historical behaviour of not allowing the
|
|
|
|
|
user to edit the merge log message. They will see an editor opened when
|
|
|
|
|
they run `git merge` to merge an annotated tag. To make it easier to adjust
|
|
|
|
|
such scripts to the updated behaviour, the environment variable
|
|
|
|
|
`GIT_MERGE_AUTOEDIT` can be set to `no` at the beginning of them.
|
2011-10-08 18:39:52 +00:00
|
|
|
|
2009-10-22 19:25:20 +00:00
|
|
|
--ff::
|
2012-02-22 22:27:07 +00:00
|
|
|
When the merge resolves as a fast-forward, only update the branch
|
|
|
|
|
pointer, without creating a merge commit. This is the default
|
|
|
|
|
behavior.
|
|
|
|
|
|
2009-10-22 19:25:20 +00:00
|
|
|
--no-ff::
|
2012-02-22 22:27:07 +00:00
|
|
|
Create a merge commit even when the merge resolves as a
|
|
|
|
|
fast-forward.
|
|
|
|
|
|
|
|
|
|
--ff-only::
|
|
|
|
|
Refuse to merge and exit with a non-zero status unless the
|
|
|
|
|
current `HEAD` is already up-to-date or the merge can be
|
|
|
|
|
resolved as a fast-forward.
|
2008-04-06 01:23:43 +00:00
|
|
|
|
2010-09-08 17:59:54 +00:00
|
|
|
--log[=<n>]::
|
2009-10-22 19:25:20 +00:00
|
|
|
--no-log::
|
2008-04-06 01:23:46 +00:00
|
|
|
In addition to branch names, populate the log message with
|
2010-09-08 17:59:54 +00:00
|
|
|
one-line descriptions from at most <n> actual commits that are being
|
|
|
|
|
merged. See also linkgit:git-fmt-merge-msg[1].
|
2009-10-22 19:25:20 +00:00
|
|
|
+
|
|
|
|
|
With --no-log do not list one-line descriptions from the
|
|
|
|
|
actual commits being merged.
|
2008-04-06 01:23:46 +00:00
|
|
|
|
2005-11-07 05:30:56 +00:00
|
|
|
|
2009-10-22 19:25:20 +00:00
|
|
|
--stat::
|
|
|
|
|
-n::
|
|
|
|
|
--no-stat::
|
|
|
|
|
Show a diffstat at the end of the merge. The diffstat is also
|
|
|
|
|
controlled by the configuration option merge.stat.
|
|
|
|
|
+
|
|
|
|
|
With -n or --no-stat do not show a diffstat at the end of the
|
|
|
|
|
merge.
|
2007-09-23 22:51:44 +00:00
|
|
|
|
git-merge --squash
Some people tend to do many little commits on a topic branch,
recording all the trials and errors, and when the topic is
reasonably cooked well, would want to record the net effect of
the series as one commit on top of the mainline, removing the
cruft from the history. The topic is then abandoned or forked
off again from that point at the mainline.
The barebone porcelainish that comes with core git tools does
not officially support such operation, but you can fake it by
using "git pull --no-merge" when such a topic branch is not a
strict superset of the mainline, like this:
git checkout mainline
git pull --no-commit . that-topic-branch
: fix conflicts if any
rm -f .git/MERGE_HEAD
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
This however does not work when the topic branch is a fast
forward of the mainline, because normal "git pull" will never
create a merge commit in such a case, and there is nothing
special --no-commit could do to begin with.
This patch introduces a new option, --squash, to support such a
workflow officially in both fast-forward case and true merge
case. The user-level operation would be the same in both cases:
git checkout mainline
git pull --squash . that-topic-branch
: fix conflicts if any -- naturally, there would be
: no conflict if fast forward.
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
When the current branch is already up-to-date with respect to
the other branch, there truly is nothing to do, so the new
option does not have any effect.
This was brought up in #git IRC channel recently.
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-06-23 08:37:02 +00:00
|
|
|
--squash::
|
2009-10-22 19:25:20 +00:00
|
|
|
--no-squash::
|
git-merge --squash
Some people tend to do many little commits on a topic branch,
recording all the trials and errors, and when the topic is
reasonably cooked well, would want to record the net effect of
the series as one commit on top of the mainline, removing the
cruft from the history. The topic is then abandoned or forked
off again from that point at the mainline.
The barebone porcelainish that comes with core git tools does
not officially support such operation, but you can fake it by
using "git pull --no-merge" when such a topic branch is not a
strict superset of the mainline, like this:
git checkout mainline
git pull --no-commit . that-topic-branch
: fix conflicts if any
rm -f .git/MERGE_HEAD
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
This however does not work when the topic branch is a fast
forward of the mainline, because normal "git pull" will never
create a merge commit in such a case, and there is nothing
special --no-commit could do to begin with.
This patch introduces a new option, --squash, to support such a
workflow officially in both fast-forward case and true merge
case. The user-level operation would be the same in both cases:
git checkout mainline
git pull --squash . that-topic-branch
: fix conflicts if any -- naturally, there would be
: no conflict if fast forward.
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
When the current branch is already up-to-date with respect to
the other branch, there truly is nothing to do, so the new
option does not have any effect.
This was brought up in #git IRC channel recently.
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-06-23 08:37:02 +00:00
|
|
|
Produce the working tree and index state as if a real
|
2009-05-25 16:00:10 +00:00
|
|
|
merge happened (except for the merge information),
|
|
|
|
|
but do not actually make a commit or
|
git-merge --squash
Some people tend to do many little commits on a topic branch,
recording all the trials and errors, and when the topic is
reasonably cooked well, would want to record the net effect of
the series as one commit on top of the mainline, removing the
cruft from the history. The topic is then abandoned or forked
off again from that point at the mainline.
The barebone porcelainish that comes with core git tools does
not officially support such operation, but you can fake it by
using "git pull --no-merge" when such a topic branch is not a
strict superset of the mainline, like this:
git checkout mainline
git pull --no-commit . that-topic-branch
: fix conflicts if any
rm -f .git/MERGE_HEAD
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
This however does not work when the topic branch is a fast
forward of the mainline, because normal "git pull" will never
create a merge commit in such a case, and there is nothing
special --no-commit could do to begin with.
This patch introduces a new option, --squash, to support such a
workflow officially in both fast-forward case and true merge
case. The user-level operation would be the same in both cases:
git checkout mainline
git pull --squash . that-topic-branch
: fix conflicts if any -- naturally, there would be
: no conflict if fast forward.
git commit -a -m 'consolidated commit log message'
git branch -f that-topic-branch ;# now fully merged
When the current branch is already up-to-date with respect to
the other branch, there truly is nothing to do, so the new
option does not have any effect.
This was brought up in #git IRC channel recently.
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-06-23 08:37:02 +00:00
|
|
|
move the `HEAD`, nor record `$GIT_DIR/MERGE_HEAD` to
|
|
|
|
|
cause the next `git commit` command to create a merge
|
|
|
|
|
commit. This allows you to create a single commit on
|
|
|
|
|
top of the current branch whose effect is the same as
|
|
|
|
|
merging another branch (or more in case of an octopus).
|
2009-10-22 19:25:20 +00:00
|
|
|
+
|
|
|
|
|
With --no-squash perform the merge and commit the result. This
|
|
|
|
|
option can be used to override --squash.
|
2007-09-23 22:51:45 +00:00
|
|
|
|
2008-06-08 01:36:09 +00:00
|
|
|
-s <strategy>::
|
|
|
|
|
--strategy=<strategy>::
|
2005-11-07 05:30:56 +00:00
|
|
|
Use the given merge strategy; can be supplied more than
|
|
|
|
|
once to specify them in the order they should be tried.
|
|
|
|
|
If there is no `-s` option, a built-in list of strategies
|
2010-01-09 23:33:00 +00:00
|
|
|
is used instead ('git merge-recursive' when merging a single
|
|
|
|
|
head, 'git merge-octopus' otherwise).
|
2009-10-22 19:25:20 +00:00
|
|
|
|
2010-04-12 16:28:13 +00:00
|
|
|
-X <option>::
|
|
|
|
|
--strategy-option=<option>::
|
|
|
|
|
Pass merge strategy specific option through to the merge
|
|
|
|
|
strategy.
|
|
|
|
|
|
2009-10-22 19:25:20 +00:00
|
|
|
--summary::
|
|
|
|
|
--no-summary::
|
|
|
|
|
Synonyms to --stat and --no-stat; these are deprecated and will be
|
|
|
|
|
removed in the future.
|
|
|
|
|
|
2010-02-24 12:50:21 +00:00
|
|
|
ifndef::git-pull[]
|
2009-10-22 19:25:20 +00:00
|
|
|
-q::
|
|
|
|
|
--quiet::
|
2011-02-20 09:53:21 +00:00
|
|
|
Operate quietly. Implies --no-progress.
|
2009-10-22 19:25:20 +00:00
|
|
|
|
|
|
|
|
-v::
|
|
|
|
|
--verbose::
|
|
|
|
|
Be verbose.
|
2011-02-20 09:53:21 +00:00
|
|
|
|
|
|
|
|
--progress::
|
|
|
|
|
--no-progress::
|
|
|
|
|
Turn progress on/off explicitly. If neither is specified,
|
|
|
|
|
progress is shown if standard error is connected to a terminal.
|
|
|
|
|
Note that not all merge strategies may support progress
|
|
|
|
|
reporting.
|
|
|
|
|
|
2010-02-24 12:50:21 +00:00
|
|
|
endif::git-pull[]
|