From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Bob Feng <bob.c.feng@intel.com>, Liming Gao <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH v2] BaseTools/Conf/gitattributes: fix "--function-context" for C source code
Date: Mon, 20 Jan 2020 10:12:10 +0000 [thread overview]
Message-ID: <20200120101210.GR15141@bivouac.eciton.net> (raw)
In-Reply-To: <20200120094245.9010-1-lersek@redhat.com>
On Mon, Jan 20, 2020 at 10:42:45 +0100, Laszlo Ersek wrote:
> The "--function-context" ("-W") option of git-diff displays the entire
> body of a modified function, not just small modified hunks within the
> function. It is useful for reviewers when the code changes to the function
> are small, but they could affect, or depend on, control flow that is far
> away in the same function.
>
> Of course, the size of the displayed context can be controlled with the
> "-U" option anyway, but such fixed-size contexts are usually either too
> small, or too large, in the above scenario.
>
> It turns out that "--function-context" does not work correctly for C
> source files in edk2. In particular, labels for the goto instruction
> (which the edk2 coding style places in the leftmost column) appear to
> terminate "--function-context".
>
> The "git" utility contains built-in hunk header patterns for the C and C++
> languages. However, they do not take effect in edk2 because we don't
> explicitly assign the "cpp" git-diff driver to our C files. The
> gitattributes(5) manual explains that this is required:
>
> > There are a few built-in patterns to make this easier, and
> > tex is one of them, so you do not have to write the above in
> > your configuration file (you still need to enable this with
> > the attribute mechanism, via .gitattributes). The following
> > built in patterns are available:
> >
> > [...]
> >
> > * cpp suitable for source code in the C and C++
> > languages.
>
> The key statement is the one in parentheses.
>
> Grab the suffix lists from the [C-Code-File] and [Acpi-Table-Code-File]
> sections of "BaseTools/Conf/build_rule.template", add "*.h" and "*.H", and
> mark those as belonging to the "cpp" git-diff driver.
>
> This change has a dramatic effect on the following command, for example:
>
> $ git show -W 2ef0c27cb84c
>
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Liming Gao <liming.gao@intel.com>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Leif Lindholm <leif@nuviainc.com>
also
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
(if it jars too much to use a different one from Cc: tag above)
For other purposes, the Linaro address can now be considered retired.
/
Leif
> ---
>
> Notes:
> v2:
>
> - take suffixes from "BaseTools/Conf/build_rule.template" [Leif]
>
> - replace "*.h" / "*.c" in the commit message with "C source" and
> [C-Code-File] / [Acpi-Table-Code-File]
>
> - Supersedes: <20200116184929.18020-1-lersek@redhat.com>
> http://mid.mail-archive.com/20200116184929.18020-1-lersek@redhat.com
> https://edk2.groups.io/g/devel/message/53312
>
> BaseTools/Conf/gitattributes | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/BaseTools/Conf/gitattributes b/BaseTools/Conf/gitattributes
> index 58b93e9d4c27..319e89064133 100644
> --- a/BaseTools/Conf/gitattributes
> +++ b/BaseTools/Conf/gitattributes
> @@ -17,3 +17,14 @@
> *.fdf diff=ini
> *.fdf.inc diff=ini
> *.inf diff=ini
> +*.c diff=cpp
> +*.C diff=cpp
> +*.cc diff=cpp
> +*.CC diff=cpp
> +*.cpp diff=cpp
> +*.Cpp diff=cpp
> +*.CPP diff=cpp
> +*.aslc diff=cpp
> +*.act diff=cpp
> +*.h diff=cpp
> +*.H diff=cpp
> --
> 2.19.1.3.g30247aa5d201
>
>
>
>
next prev parent reply other threads:[~2020-01-20 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 9:42 [PATCH v2] BaseTools/Conf/gitattributes: fix "--function-context" for C source code Laszlo Ersek
2020-01-20 10:12 ` Leif Lindholm [this message]
2020-01-20 11:56 ` [edk2-devel] " Laszlo Ersek
2020-01-23 12:13 ` Laszlo Ersek
2020-01-31 8:33 ` Laszlo Ersek
2020-01-31 8:35 ` Liming Gao
2020-01-31 16:50 ` Laszlo Ersek
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-list 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=20200120101210.GR15141@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox