Thread (7 messages) 7 messages, 4 authors, 2016-06-15

Re: git diff - no newline after @@ ?

From: Jeff King <hidden>
Date: 2016-06-15 22:42:37

On Fri, Aug 18, 2006 at 02:37:42PM +0200, Petr Sebor wrote:
quoted
quoted
has anyone noticed that the 'git diff' output somehow lacks the newline
after the @@ tag?
Why should it? It's hunk comment.
Hunk comment? Maybe we don't understand each other...
The intent of a hunk comment is to give the user some context. Note how
it's usually the C function name, even if the declaration of that
function isn't the line right before the context lines?
quoted hunk ↗ jump to hunk
check another example:
--- a/include/linux/kernel.h
+++ b/include/linux/kernel.h
@@ -13,6 +13,7 @@ #include <linux/stddef.h>
#include <linux/types.h>
#include <linux/compiler.h>
#include <linux/bitops.h>
+#include <linux/memleak.h>
#include <asm/byteorder.h>
#include <asm/bug.h>
The function detection is very simple (I believe it just looks for the
closest preceding line without any prior whitespace).
whereas gnu diff would output
Try diff -p to get a hunk comment.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help