From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] gitattributes: Cover Objective-C source files
Date: Fri, 18 Mar 2022 23:42:52 +0900 [thread overview]
Message-ID: <69c6db77-273e-dbeb-e695-e20772d003e2@gmail.com> (raw)
In-Reply-To: <62dbdfcf-771e-7c84-ab8b-b02a61112f86@gmail.com>
I don't think this is needed. I could see a diff annotated with a method
name even without this change:
% git diff
diff --git a/ui/cocoa.m b/ui/cocoa.m
index cb6e7c41dc6..14a4416cc8b 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -1264,6 +1264,7 @@ - (id) init
[pauseLabel setTextColor: [NSColor blackColor]];
[pauseLabel sizeToFit];
}
+ //
return self;
}
Commit 29cf16db23 says:
> Since commits 0979ed017f0 ("meson: rename .inc.h files to .h.inc")
> and 139c1837db7 ("meson: rename included C source files to .c.inc")
> 'git-diff --function-context' stopped displaying C function context
> correctly.
So I suspect Git has some knowledge of common file extensions like .c,
.h and .m although I couldn't find in the source code of Git.
Regards,
Akihiko Odaki
On 2022/03/18 23:10, Philippe Mathieu-Daudé wrote:
> +qemu-trivial@
>
> On 17/3/22 14:03, Philippe Mathieu-Daudé wrote:
>> From: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>
>> See comments in commit 29cf16db23 ("buildsys: Help git-diff
>> adding .gitattributes config file") for details.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> .gitattributes | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/.gitattributes b/.gitattributes
>> index 07f430e944..a217cb7bfe 100644
>> --- a/.gitattributes
>> +++ b/.gitattributes
>> @@ -1,3 +1,4 @@
>> *.c.inc diff=c
>> *.h.inc diff=c
>> +*.m diff=objc
>> *.py diff=python
>
next prev parent reply other threads:[~2022-03-18 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 13:03 [PATCH] gitattributes: Cover Objective-C source files Philippe Mathieu-Daudé
2022-03-18 14:10 ` Philippe Mathieu-Daudé
2022-03-18 14:10 ` Philippe Mathieu-Daudé
2022-03-18 14:42 ` Akihiko Odaki [this message]
2022-03-18 16:14 ` Philippe Mathieu-Daudé
2022-03-19 3:25 ` Akihiko Odaki
2022-03-19 3:25 ` Akihiko Odaki
2022-03-19 13:49 ` Philippe Mathieu-Daudé
2022-03-19 13:49 ` Philippe Mathieu-Daudé
2022-03-19 14:03 ` Akihiko Odaki
2022-03-19 14:03 ` Akihiko Odaki
2022-03-18 14:36 ` Christian Schoenebeck
2022-03-28 22:30 ` Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69c6db77-273e-dbeb-e695-e20772d003e2@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=qemu_oss@crudebyte.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.