From: Philippe Blain <levraiphilippeblain@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Thomas Rast <tr@thomasrast.ch>,
Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 1/2] Documentation/git-log: document accepted line-log diff formats
Date: Tue, 17 Dec 2019 21:44:01 -0500 [thread overview]
Message-ID: <E3047E9B-B269-4DC3-A894-BB39C7A20E77@gmail.com> (raw)
In-Reply-To: <20191217113301.GA8609@szeder.dev>
That’s a good point. I did not think of such corner cases. I will remove that mention then.
> Le 17 déc. 2019 à 06:33, SZEDER Gábor <szeder.dev@gmail.com> a écrit :
>
> On Tue, Dec 17, 2019 at 05:07:42AM +0000, Philippe Blain via GitGitGadget wrote:
>> From: Philippe Blain <levraiphilippeblain@gmail.com>
>>
>> Currently the line-log functionality (git log -L) only supports
>> displaying patch output (`-p`, its default behavior) and suppressing it
>> (`-s`). A check was added in the code to that effect in 5314efaea (line-log:
>> detect unsupported formats, 2019-03-10) but the documentation was not
>> updated.
>>
>> Explicitly mention that `-L` implies `-p`, that patch output can be
>> suppressed using `-s`, and that all other diff formats are not allowed.
>>
>> Additionnally, mention that the ':<funcname>' form implies `--function-context`.
>>
>> Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
>> ---
>> Documentation/git-log.txt | 6 +++++-
>> Documentation/gitk.txt | 6 +++++-
>> 2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
>> index b406bc4c48..1c52bf184d 100644
>> --- a/Documentation/git-log.txt
>> +++ b/Documentation/git-log.txt
>> @@ -77,7 +77,11 @@ produced by `--stat`, etc.
>> not give any pathspec limiters. This is currently limited to
>> a walk starting from a single revision, i.e., you may only
>> give zero or one positive revision arguments.
>> - You can specify this option more than once.
>> + You can specify this option more than once. Implies `--patch`.
>> + If ``:<funcname>'' is given, implies `--function-context`.
>
> ':<funcname>' doesn't imply '--function-context', but defines a line
> range starting at the function-name-looking line that first matches
> "funcname" and ending just before the next function-name-looking line,
> and line-log will then show that line range as context for each
> commit. Although in many cases it shows diffs that look like as if
> '--function-context' were given, there are corner cases where they
> clearly differ, e.g. when following the history of a function that was
> at one point combined with the function directly below it.
>
> Note the two commits in the middle that show two functions although
> only one of them was actually modified in each of those commits:
>
> $ git log --oneline -L:func:file.c
> 04b0c16 Combine funcA() and funcB() into func()
>
> diff --git a/file.c b/file.c
> --- a/file.c
> +++ b/file.c
> @@ -1,9 +1,4 @@
> -int funcA()
> +int func()
> {
> - return A;
> -}
> -
> -int funcB()
> -{
> - return B;
> + return A + B;
> }
> ed0d4d9 Modify funcB()
>
> diff --git a/file.c b/file.c
> --- a/file.c
> +++ b/file.c
> @@ -1,9 +1,9 @@
> int funcA()
> {
> return A;
> }
>
> int funcB()
> {
> - return b;
> + return B;
> }
> 0d4e9b5 Modify funcA()
>
> diff --git a/file.c b/file.c
> --- a/file.c
> +++ b/file.c
> @@ -1,9 +1,9 @@
> int funcA()
> {
> - return a;
> + return A;
> }
>
> int funcB()
> {
> return b;
> }
> c3f8a44 Add funcA() and funcB()
>
> diff --git a/file.c b/file.c
> --- /dev/null
> +++ b/file.c
> @@ -0,0 +1,9 @@
> +int funcA()
> +{
> + return a;
> +}
> +
> +int funcB()
> +{
> + return b;
> +}
>
> Now compare that to the same two middle commits shown with '-p
> --function-context', which doesn't show the unmodified function:
>
> $ git log --oneline -p --function-context file.c
> 04b0c16 Combine funcA() and funcB() into func()
> diff --git a/file.c b/file.c
> index 89571b3..33301ea 100644
> --- a/file.c
> +++ b/file.c
> @@ -1,9 +1,4 @@
> -int funcA()
> +int func()
> {
> - return A;
> -}
> -
> -int funcB()
> -{
> - return B;
> + return A + B;
> }
> ed0d4d9 Modify funcB()
> diff --git a/file.c b/file.c
> index 13592c8..89571b3 100644
> --- a/file.c
> +++ b/file.c
> @@ -5,5 +5,5 @@ int funcA()
>
> int funcB()
> {
> - return b;
> + return B;
> }
> 0d4e9b5 Modify funcA()
> diff --git a/file.c b/file.c
> index 11e1e87..13592c8 100644
> --- a/file.c
> +++ b/file.c
> @@ -1,6 +1,6 @@
> int funcA()
> {
> - return a;
> + return A;
> }
>
> int funcB()
> c3f8a44 Add funcA() and funcB()
> diff --git a/file.c b/file.c
> new file mode 100644
> index 0000000..11e1e87
> --- /dev/null
> +++ b/file.c
> @@ -0,0 +1,9 @@
> +int funcA()
> +{
> + return a;
> +}
> +
> +int funcB()
> +{
> + return b;
> +}
next prev parent reply other threads:[~2019-12-18 2:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 5:07 [PATCH 0/2] Improve line log documentation Philippe Blain via GitGitGadget
2019-12-17 5:07 ` [PATCH 1/2] Documentation/git-log: document accepted line-log diff formats Philippe Blain via GitGitGadget
2019-12-17 11:33 ` SZEDER Gábor
2019-12-18 2:44 ` Philippe Blain [this message]
2019-12-17 15:33 ` Derrick Stolee
2019-12-18 2:47 ` Philippe Blain
2019-12-17 5:07 ` [PATCH 2/2] Documentation/git-log: mention that line-log regex must match in starting revision Philippe Blain via GitGitGadget
2019-12-17 15:34 ` Derrick Stolee
2019-12-17 18:16 ` Junio C Hamano
2019-12-18 3:28 ` Philippe Blain
2019-12-18 10:55 ` Derrick Stolee
2019-12-18 11:49 ` SZEDER Gábor
2019-12-18 17:59 ` Junio C Hamano
2019-12-26 17:46 ` Philippe Blain
2019-12-18 11:09 ` SZEDER Gábor
2019-12-26 17:43 ` [PATCH v2 0/2] Improve line log documentation Philippe Blain via GitGitGadget
2019-12-26 17:43 ` [PATCH v2 1/2] doc: log, gitk: document accepted line-log diff formats Philippe Blain via GitGitGadget
2019-12-26 17:43 ` [PATCH v2 2/2] doc: log, gitk: line-log arguments must exist in starting revision Philippe Blain via GitGitGadget
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E3047E9B-B269-4DC3-A894-BB39C7A20E77@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).