stg-refresh(1) [debian man page]

STG-REFRESH(1)							   StGit Manual 						    STG-REFRESH(1)

NAME

       stg-refresh - Generate a new commit for the current patch

SYNOPSIS

       stg refresh [options] [<files or dirs>]

DESCRIPTION

       Include the latest work tree and index changes in the current patch. This command generates a new git commit object for the patch; the old
       commit is no longer visible.

       You may optionally list one or more files or directories relative to the current working directory; if you do, only matching files will be
       updated.

       Behind the scenes, stg refresh first creates a new temporary patch with your updates, and then merges that patch into the patch you asked
       to have refreshed. If you asked to refresh a patch other than the topmost patch, there can be conflicts; in that case, the temporary patch
       will be left for you to take care of, for example with stg squash.

       The creation of the temporary patch is recorded in a separate entry in the patch stack log; this means that one undo step will undo the
       merge between the other patch and the temp patch, and two undo steps will additionally get rid of the temp patch.

OPTIONS

       -u, --update
	   Only update the current patch files.

       -i, --index
	   Instead of setting the patch top to the current contents of the worktree, set it to the current contents of the index.

       -p PATCH, --patch PATCH
	   Refresh (applied) PATCH instead of the top patch.

       -e, --edit
	   Invoke an editor for the patch description.

       -a NOTE, --annotate NOTE
	   Annotate the patch log entry.

       -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.

       --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.

STGIT

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

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

GIT-PATCH-ID(1)                                                     Git Manual                                                     GIT-PATCH-ID(1)

NAME

       git-patch-id - Compute unique ID for a patch

SYNOPSIS

       git patch-id [--stable | --unstable]

DESCRIPTION

       Read a patch from the standard input and compute the patch ID for it.

       A "patch ID" is nothing but a sum of SHA-1 of the file diffs associated with a patch, with whitespace and line numbers ignored. As such,
       it's "reasonably stable", but at the same time also reasonably unique, i.e., two patches that have the same "patch ID" are almost
       guaranteed to be the same thing.

       IOW, you can use this thing to look for likely duplicate commits.

       When dealing with git diff-tree output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and
       outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. This can be used to make
       a mapping from patch ID to commit ID.

OPTIONS

       --stable
           Use a "stable" sum of hashes as the patch ID. With this option:

           o   Reordering file diffs that make up a patch does not affect the ID. In particular, two patches produced by comparing the same two
               trees with two different settings for "-O<orderfile>" result in the same patch ID signature, thereby allowing the computed result
               to be used as a key to index some meta-information about the change between the two trees;

           o   Result is different from the value produced by git 1.9 and older or produced when an "unstable" hash (see --unstable below) is
               configured - even when used on a diff output taken without any use of "-O<orderfile>", thereby making existing databases storing
               such "unstable" or historical patch-ids unusable.

                   This is the default if patchid.stable is set to true.

       --unstable
           Use an "unstable" hash as the patch ID. With this option, the result produced is compatible with the patch-id value produced by git 1.9
           and older. Users with pre-existing databases storing patch-ids produced by git 1.9 and older (who do not deal with reordered patches)
           may want to use this option.

               This is the default.

GIT

       Part of the git(1) suite

Git 2.17.1                                                          10/05/2018                                                     GIT-PATCH-ID(1)