git-commit/git-applypatch whitespace rules different?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



git-commit/git-applypatch whitespace rules seem to be different.
Is this expected?

Example:
I take a patch, apply it and commit without warnings about whitespace:

$patch -p1 -i /tmp/ipoib_cm.patc
$git commit drivers/infiniband/ulp/ipoib/
Created commit f83bc11fd3cadb0b3f27d31fbaaa1a5d409e65d9
 8 files changed, 339 insertions(+), 31 deletions(-)

but when try git-applypatch:

$git-applypatch test1 /tmp/ipoib_cm.patch test1

Space in indent is followed by a tab.
/tmp/ipoib_cm.patch:174:                test_bit(IPOIB_FLAG_ADMIN_CM,
						 &priv->flags);
Space in indent is followed by a tab.
/tmp/ipoib_cm.patch:181:                test_bit(IPOIB_FLAG_ADMIN_CM,
						 &priv->flags);
Adds trailing whitespace.
/tmp/ipoib_cm.patch:256:        return;
Space in indent is followed by a tab.
/tmp/ipoib_cm.patch:610:                        ret = 0; /* Connection is going
							    away already. */
Space in indent is followed by a tab.
/tmp/ipoib_cm.patch:1227:               neigh = tx->neigh;


why is not git-commit not warning me? I did not set --no-verify ...

-- 
MST
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]