git2cl(1) [debian man page]

GIT2CL(1)						      General Commands Manual							 GIT2CL(1)

NAME

       git2cl - tool to convert git logs to GNU ChangeLog

DESCRIPTION

       This is a quick'n'dirty tool to convert git logs to GNU ChangeLog format.

       The tool invokes git log internally unless you pipe a log to it.  Thus, typically you would use it as follows:

SYNOPSIS

       git2cl > ChangeLog

       If  you don't want git2cl to invoke git log internally, you can use it as a pipe.  It needs a git log generated with --pretty --numstat and
       --summary.  You can use it as follows:

       git log --pretty --numstat --summary | git2cl > ChangeLog

SEE ALSO

       README in /usr/share/doc/git2cl.

       Output format specification: <http://www.gnu.org/prep/standards/html_node/Change-Logs.html>

AUTHORS

       git2cl is developed by Simon Josefsson <simon@josefsson.org> and Luis Mondesi <lemsx1@gmail.com>

       This man page was written by Dmitry Smirnov <onlyjob@member.fsf.org> for Debian GNU/Linux (but may be used by others).

git2cl								   November 2011							 GIT2CL(1)

GIT-FMT-MERGE-MSG(1)						    Git Manual						      GIT-FMT-MERGE-MSG(1)

NAME

       git-fmt-merge-msg - Produce a merge commit message

SYNOPSIS

       git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log]
       git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log] -F <file>

DESCRIPTION

       Takes the list of merged objects on stdin and produces a suitable commit message to be used for the merge commit, usually to be passed as
       the <merge-message> argument of git merge.

       This command is intended mostly for internal use by scripts automatically invoking git merge.

OPTIONS

       --log[=<n>]
	   In addition to branch names, populate the log message with one-line descriptions from the actual commits that are being merged. At most
	   <n> commits from each merge parent will be used (20 if <n> is omitted). This overrides the merge.log configuration variable.

       --no-log
	   Do not list one-line descriptions from the actual commits being merged.

       --[no-]summary
	   Synonyms to --log and --no-log; these are deprecated and will be removed in the future.

       -m <message>, --message <message>
	   Use <message> instead of the branch names for the first line of the log message. For use with --log.

       -F <file>, --file <file>
	   Take the list of merged objects from <file> instead of stdin.

CONFIGURATION

       merge.branchdesc
	   In addition to branch names, populate the log message with the branch description text associated with them. Defaults to false.

       merge.log
	   In addition to branch names, populate the log message with at most the specified number of one-line descriptions from the actual
	   commits that are being merged. Defaults to false, and true is a synonym for 20.

       merge.summary
	   Synonym to merge.log; this is deprecated and will be removed in the future.

EXAMPLE

	   $ git fetch origin master
	   $ git fmt-merge-msg --log <$GIT_DIR/FETCH_HEAD

       Print a log message describing a merge of the "master" branch from the "origin" remote.

SEE ALSO

       git-merge(1)

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						      GIT-FMT-MERGE-MSG(1)