From: Junio C Hamano <gitster@pobox.com>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] blame: add option to print tips (--tips)
Date: Sun, 22 Jan 2017 14:58:21 -0800 [thread overview]
Message-ID: <xmqq1svuvh0y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAOc6etaQ-fDWn38YzXkGOC0fSan1vrxjVDUXS924nBXWTTrhNQ@mail.gmail.com> (Edmundo Carmona Antoranz's message of "Sun, 22 Jan 2017 15:39:29 -0600")
Edmundo Carmona Antoranz <eantoranz@gmail.com> writes:
> So, this is a draft of what I mean by "adding tips to blame".
>
> Example output (sample from builtin/blame.c):
> ...
> 15:32 $ ./git blame --tips -L 1934,1960 builtin/blame.c
> cee7f245dc: git-pickaxe: blame rewritten.
> cee7f245dc builtin-pickaxe.c (Junio C Hamano 2006-10-19
> 16:00:04 -0700 1934)
This is unfortunately unreadable to guess what you wanted to
achieve, not because the lines are too wide, but because they are
line-wrapped.
> Does it look "worthy"? And if so, would it be better to think of
> something like an "aggregate" option (or something like that) that
> would include the common information as tips, something like:
What is the target audience? If you are trying to write a script
that reads output by "git blame", you are strongly discouraged
unless you are reading from "git blame --porcelain" which is more
compact and has this information already IIRC.
next prev parent reply other threads:[~2017-01-22 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 21:28 [PATCH] blame: add option to print tips (--tips) Edmundo Carmona Antoranz
2017-01-22 21:39 ` Edmundo Carmona Antoranz
2017-01-22 22:58 ` Junio C Hamano [this message]
2017-01-22 23:04 ` Edmundo Carmona Antoranz
2017-01-22 23:35 ` Junio C Hamano
2017-01-23 16:33 ` Pranit Bauva
2017-01-23 18:36 ` Junio C Hamano
2017-01-24 11:36 ` Pranit Bauva
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=xmqq1svuvh0y.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=eantoranz@gmail.com \
--cc=git@vger.kernel.org \
/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