From: Kyle Meyer <firstname.lastname@example.org> To: ian martins <email@example.com> Cc: Org-Mode mailing list <firstname.lastname@example.org> Subject: Re: [PATCH] ob-java.el: Allow for more whitespace Date: Sat, 14 Nov 2020 13:21:53 -0500 Message-ID: <email@example.com> (raw) In-Reply-To: <CAC=rjb7G2noq9vm_-LVRN-BLu9uO2+So4A0Np_n6m3i=dfHt=Q@mail.gmail.com> ian martins writes: > On Thu, Nov 12, 2020 at 10:46 PM Kyle Meyer <firstname.lastname@example.org> wrote: >> Is this related to Jarmo's report at >> <https://email@example.com>? 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" territory... 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 underneath: 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 example $ 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.
next prev parent 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 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/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git