Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

guilt-patchbomb(1) [debian man page]

GUILT-PATCHBOMB(1)						   Guilt Manual 						GUILT-PATCHBOMB(1)

NAME
guilt-patchbomb - Email a series of commits interactively SYNOPSIS
guilt-patchbomb [-n] [-s] [--in-reply-to <msgid>] [--git] [--subject-prefix <prefix>] [<hash> | <since>..[<until>] | ..<until>] DESCRIPTION
Send a series of commits via email asking for To, CC and other information interactively. OPTIONS
-n Don't send -s Don't add additional repository committer sign-offs to the patch. This allows the sign-off chain to be fully expressed in the commit messages and not changed by the act of sending a patchbomb. --in-reply-to <msgid> Set the In-reply-to header to the specified message id. This allows the patches to be sent as replies to an arbitrary message. --git Generate a patch which uses all the features offered by the git diff format (e.g., rename and copy detection). --subject-prefix <prefix> Rather than using the standard [PATCH] prefix in the subject line, use [<prefix>] instead. <hash> Only the specified revision. <since>..[<until>] Revisions starting from <since> until <until>. The <since> revision it self is NOT included, while <until> is. If <until> is not specified, it is assumed to be HEAD. ..<until> All revisions until the <until> revision (inclusive). AUTHOR
Written by Josef "Jeff" Sipek <jeffpc@josefsipek.net[1]> DOCUMENTATION
Documentation by Brandon Philips <brandon@ifup.org[2]> GUILT
Part of the guilt(7) suite (Generated for Guilt v0.35) NOTES
1. jeffpc@josefsipek.net mailto:jeffpc@josefsipek.net 2. brandon@ifup.org mailto:brandon@ifup.org Guilt v0.35 01/20/2013 GUILT-PATCHBOMB(1)

Check Out this Related Man Page

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

NAME
git-patch-id - Compute unique ID for a patch SYNOPSIS
git patch-id < <patch> DESCRIPTION
A "patch ID" is nothing but a SHA1 of the diff 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
<patch> The diff to create the ID of. AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>. GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org 2. git@vger.kernel.org mailto:git@vger.kernel.org Git 1.7.1 07/05/2010 GIT-PATCH-ID(1)
Man Page

Featured Tech Videos