From: Junio C Hamano <gitster@pobox.com>
To: issac.trotts@gmail.com
Cc: git@vger.kernel.org, noemi@sourcegraph.com,
Issac Trotts <issactrotts@google.com>
Subject: Re: [PATCH] log: add %S option (like --source) to log --format
Date: Tue, 08 Jan 2019 14:21:40 -0800 [thread overview]
Message-ID: <xmqqmuoa4wp7.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190108132048.57142-1-issactrotts@google.com> (issac trotts's message of "Wed, 9 Jan 2019 00:20:48 +1100")
issac.trotts@gmail.com writes:
> From: Issac Trotts <issac.trotts@gmail.com>
Heh, I'll edit this line to match S-o-b: below.
>
> Make it possible to write for example
>
> git log --format="%H,%S"
>
> where the %S at the end is a new placeholder that prints out the ref
> (tag/branch) for each commit.
>
> Using %d might seem like an alternative but it only shows the ref for the last
> commit in the branch.
>
> Signed-off-by: Issac Trotts <issactrotts@google.com>
>
> ---
> diff --git a/log-tree.c b/log-tree.c
> index 10680c139..3cb14256e 100644
> --- a/log-tree.c
> +++ b/log-tree.c
> @@ -700,6 +700,7 @@ void show_log(struct rev_info *opt)
> ctx.color = opt->diffopt.use_color;
> ctx.expand_tabs_in_log = opt->expand_tabs_in_log;
> ctx.output_encoding = get_log_output_encoding();
> + ctx.rev = opt;
There are quite a few existing codepaths that change their behaviour
based on NULL-ness of ctx.rev field. How would we make sure that
this change have no unintended consequence, I wonder?
> + case 'S': /* tag/branch like --source */
> + if (c->pretty_ctx->rev == NULL || c->pretty_ctx->rev->sources == NULL) {
> + return 0;
> + }
> + slot = revision_sources_at(c->pretty_ctx->rev->sources, commit);
> + if (!(slot && *slot)) {
> + return 0;
> + }
> + strbuf_addstr(sb, *slot);
> + return 1;
Let's update the style of this hunk here like so:
if (!c->pretty_ctx->rev || !c->pretty_ctx->rev->sources)
return 0;
slot = ...;
if (!(slot && *slot))
return 0;
strbuf_addstr(...);
return 1;
I wonder if it is even better to apply de-Morgan to one of the above
two, i.e.
if (!(c->pretty_ctx->rev && c->pretty_ctx->rev->sources))
return 0;
Anyway, thanks. Will queue.
next prev parent reply other threads:[~2019-01-08 22:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 13:20 [PATCH] log: add %S option (like --source) to log --format issac.trotts
2019-01-08 22:21 ` Junio C Hamano [this message]
2019-01-11 6:28 ` Issac Trotts
2019-01-11 17:37 ` Junio C Hamano
2019-01-11 17:47 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 6:30 issac.trotts
2018-12-31 21:48 issac.trotts
2018-12-31 4:53 issac.trotts
2019-01-02 19:33 ` Junio C Hamano
2019-01-08 13:14 ` Issac Trotts
2018-12-19 8:33 issac.trotts
2018-12-21 5:24 ` Issac Trotts
2018-12-22 22:22 ` Jeff King
2018-12-25 2:12 ` Issac Trotts
2018-12-27 13:20 ` Derrick Stolee
2018-12-28 18:14 ` Junio C Hamano
2018-12-31 4:35 ` Issac Trotts
2018-12-17 6:25 Issac Trotts
2018-12-17 9:31 ` Junio C Hamano
2018-12-18 3:35 ` Issac Trotts
2018-12-17 15:59 ` Jeff King
2018-12-18 17:14 ` Issac Trotts
2018-12-19 3:47 ` Issac Trotts
2018-12-19 8:07 ` Issac Trotts
2018-12-19 17:09 ` Issac Trotts
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=xmqqmuoa4wp7.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=issac.trotts@gmail.com \
--cc=issactrotts@google.com \
--cc=noemi@sourcegraph.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).