Staging
v0.5.2
v0.5.2
Revision e00f3790b88ce61f1bdc863011a122b98b43197e authored by Johannes Sixt on 23 May 2008, 14:13:05 UTC, committed by Junio C Hamano on 23 May 2008, 22:52:20 UTC
The intention of --symbolic-full-name is to not print anything if a
revision is not an exact ref. But this command:
$ git-rev-parse --symbolic-full-name --not master~1
still emitted a sole '^' to stdout (provided that there's no other ref at
master~1). This fixes it.
Signed-off-by: Johannes Sixt <johannes.sixt@telecom.at>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent e77b0b5
git-patch-id.txt
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 string. 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>
Documentation
--------------
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
GIT
---
Part of the linkgit:git[7] suite
Computing file changes ...
