commit-patch 2.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News commit-patch 2.1 (Default branch)
# 1  
Old 12-23-2008
commit-patch 2.1 (Default branch)

commit-patch allows the user to control exactly what gets committed to a version control system by letting the user supply a patch to be committed rather than using the files in the current working directory. This allows for more finely grained commits. It supports Darcs, Git, CVS, and Mercurial. License: GNU General Public License v2 Changes:
Git support was added. "commit-partial" was added. The --verbose and --dry-run options were added. The --message-file option was added. lsdiff on CVS subdirectories was fixed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

give ldap a/c during commit in commit line section

Is someone help me to achieve my goal I am working on a script actually script is working fine .The goal of script is restrict the user for something like while he is doing tocommit in repository he will commit with comment and with some parameter....here I have one more requirement and that is... (0 Replies)
Discussion started by: anuragpgtgerman
0 Replies

2. UNIX for Advanced & Expert Users

cvs[commit aborted]:'root is not allowed to commit changes'

Hi , can u please any one of you give solution for this .. when am tryring to commit files from the CVS in Myeclipse J2ee Environment . that i coundnt able to commit and getting the Following error message cvs :'root' is not allowd to commit files' am using redhat enterprise 5 Server . (1 Reply)
Discussion started by: rksubash
1 Replies
Login or Register to Ask a Question
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)