stg-publish(1) [debian man page]

STG-PUBLISH(1)							   StGit Manual 						    STG-PUBLISH(1)

NAME

       stg-publish - Push the stack changes to a merge-friendly branch

SYNOPSIS

       stg publish [options] [branch]

DESCRIPTION

       This command commits a set of changes on a separate (called public) branch based on the modifications of the given or current stack. The
       history of the public branch is not re-written, making it merge-friendly and feasible for publishing. The heads of the stack and public
       branch may be different but the corresponding tree objects are always the same.

       If the trees of the stack and public branch are different (otherwise the command has no effect), StGit first checks for a rebase of the
       stack since the last publishing. If a rebase is detected, StGit creates a commit on the public branch corresponding to a merge between the
       new stack base and the latest public head.

       If no rebasing was detected, StGit checks for new patches that may have been created on top of the stack since the last publishing. If new
       patches are found and are not empty, they are checked into the public branch keeping the same commit information (e.g. log message, author,
       committer, date).

       If the above tests fail (e.g. patches modified or removed), StGit creates a new commit on the public branch having the same tree as the
       stack but the public head as its parent. The editor will be invoked if no "--message" option is given.

       It is recommended that stack modifications falling in different categories as described above are separated by a publish command in order
       to keep the public branch history cleaner (otherwise StGit would generate a big commit including several stack modifications).

       The public branch name can be set via the branch.<branch>.public configuration variable (defaulting to "<branch>.public").

OPTIONS

       -b BRANCH, --branch BRANCH
	   Use BRANCH instead of the default branch.

       --author "NAME <EMAIL>"
	   Set the author details.

       --authname NAME
	   Set the author name.

       --authemail EMAIL
	   Set the author email.

       --authdate DATE
	   Set the author date.

       -m MESSAGE, --message MESSAGE
	   Use MESSAGE instead of invoking the editor.

       -f FILE, --file FILE
	   Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)

       --sign
	   Add a "Signed-off-by:" to the end of the patch.

       --ack
	   Add an "Acked-by:" line to the end of the patch.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							    STG-PUBLISH(1)

Check Out this Related Man Page

STG-EDIT(1)							   StGit Manual 						       STG-EDIT(1)

NAME

       stg-edit - edit a patch description or diff

SYNOPSIS

       stg edit [options] [<patch>]

DESCRIPTION

       Edit the description and author information of the given patch (or the current patch if no patch name was given). With --diff, also edit
       the diff.

       The editor is invoked with the following contents:

	   From: A U Thor <author@example.com>
	   Date: creation date

	   Patch description

       If --diff was specified, the diff appears at the bottom, after a separator:

	   ---

	   Diff text

       Command-line options can be used to modify specific information without invoking the editor. (With the --edit option, the editor is invoked
       even if such command-line options are given.)

       If the patch diff is edited but does not apply, no changes are made to the patch at all. The edited patch is saved to a file which you can
       feed to "stg edit --file", once you have made sure it does apply.

OPTIONS

       -d, --diff
	   Edit the patch diff.

       -e, --edit
	   Invoke interactive editor.

       --sign
	   Add a "Signed-off-by:" to the end of the patch.

       --ack
	   Add an "Acked-by:" line to the end of the patch.

       -m MESSAGE, --message MESSAGE
	   Use MESSAGE instead of invoking the editor.

       -f FILE, --file FILE
	   Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)

       --save-template FILE
	   Instead of running the command, just write the message template to FILE, and exit. (If FILE is "-", write to stdout.)

	   When driving StGit from another program, it is often useful to first call a command with --save-template, then let the user edit the
	   message, and then call the same command with --file.

       --author "NAME <EMAIL>"
	   Set the author details.

       --authname NAME
	   Set the author name.

       --authemail EMAIL
	   Set the author email.

       --authdate DATE
	   Set the author date.

       -O OPTIONS, --diff-opts OPTIONS
	   Extra options to pass to "git diff".

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							       STG-EDIT(1)

Linux and UNIX Man Pages

stg-publish(1) [debian man page]

Check Out this Related Man Page