Org-mode mailing list
 help / color / mirror / Atom feed
From: Kyle Meyer <>
To: ian martins <>
Cc: Org-Mode mailing list <>
Subject: Re: [PATCH] ob-java.el: Allow for more whitespace
Date: Sat, 14 Nov 2020 13:21:53 -0500
Message-ID: <> (raw)
In-Reply-To: <>

ian martins writes:

> On Thu, Nov 12, 2020 at 10:46 PM Kyle Meyer <> wrote:

>> Is this related to Jarmo's report at
>> <>?  If so, it'd be good
>> to include a Reported-by trailer as well as a link.
> Yes. The updated patch includes Reported-by. That is just text in the
> commit message, not a git option, right?

Correct, it's just the block at the end of the commit message.  If you
use Magit's git-commit.el, there are some helpers for inserting common
trailers, including git-commit-reported ('C-c C-p').

The main thing is that the information is there in some form, so
everything that follows next is very much in the "doesn't really matter"

I've recently tried to be more consistent with the format I use.  In
particular, giving the link a keyword rather than putting a plain value

  Reported-by: Name <email>
  Ref: link

My reason for this is that Git does have a concept of what a trailer is
(see 'man git-interpret-trailers').  Without the "Ref:" (or some other
keyword), the link is seen as part of the Reported-by value if the link
has indentation.  Without indentation, the Reported-by is no longer seen
as a trailer.

And with Git 2.29, I've become a little more interested in Git being
able to parse these because shortlog learned "--group=trailer:".  For

  $ git shortlog -s --group=trailer:reported-by release_9.4.. | head -3
       1	Allen Li
       1	B Goodr
       1	Charles Tam

I think that's kind of neat, but again doesn't really matter :)

Thanks for the updates.

  reply	other threads:[~2020-11-14 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 10:38 ian martins
2020-11-13  3:46 ` Kyle Meyer
2020-11-14  9:40   ` ian martins
2020-11-14 18:21     ` Kyle Meyer [this message]
2020-12-14  6:11 ` Bastien

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone