From: ian martins <firstname.lastname@example.org> To: Bastien <email@example.com> Cc: Org-Mode mailing list <firstname.lastname@example.org> Subject: Re: [PATCH] ob-java Date: Sat, 24 Oct 2020 20:30:54 -0400 [thread overview] Message-ID: <CAC=rjb5Q3GZvM+QrJ=NKmffPLsdFyGk04N-db_sHvRFP3Lz6-A@mail.gmail.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1200 bytes --] This happened because the new ob-java wasn't based on the old ob-java. I wrote ob-haxe based on ob-C and ob-python and then derived ob-java from ob-haxe. I went back and forth about who should be the author of ob-haxe. I considered listing the authors of ob-C and ob-python, but I thought it wouldn't make sense since they may not have heard of haxe, and they may not like my code or want their names on it. I didn't really think about the author of the new ob-java, since it came directly from ob-haxe. But I want to follow your conventions. I will put the authors of ob-C and ob-python (Eric Schulte and Dan Davison) as the authors of ob-java and ob-haxe. The implementations are nearly the same. it wouldn't make sense for them to have different authors. On Sat, Oct 24, 2020 at 7:58 AM Bastien <firstname.lastname@example.org> wrote: > Hi Ian, > > feel free to install the patch when you think it's ready. > > One minor nitpick: > > -;; Author: Eric Schulte > -;; Maintainer: Ian Martins <email@example.com> > +;; Author: Ian Martins <firstname.lastname@example.org> > > I suggest you leave Eric Schulte as the author while adding yourself > as the maintainer, even if the "change" is a big rewrite. > > Thanks, > > -- > Bastien > [-- Attachment #2: Type: text/html, Size: 1712 bytes --]
next prev parent reply other threads:[~2020-10-25 0:33 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-05 12:35 ian martins 2020-10-05 13:23 ` ian martins 2020-10-09 11:15 ` ian martins 2020-10-20 18:28 ` John Herrlin 2020-10-20 19:17 ` John Herrlin 2020-10-21 2:37 ` ian martins 2020-10-21 5:59 ` John Herrlin 2020-10-21 12:47 ` ian martins 2020-10-21 13:54 ` John Herrlin 2020-10-22 12:23 ` ian martins 2020-10-22 12:56 ` John Herrlin 2020-10-24 17:05 ` Kyle Meyer 2020-10-25 2:10 ` ian martins 2020-10-25 2:40 ` Kyle Meyer 2020-10-25 19:36 ` ian martins 2020-11-05 16:29 ` Jarmo Hurri 2020-11-05 17:10 ` ian martins 2020-11-06 5:21 ` Jarmo Hurri 2020-11-06 23:00 ` ian martins 2020-11-09 14:06 ` Jarmo Hurri 2020-11-10 13:14 ` ian martins 2020-11-10 6:29 ` Jarmo Hurri 2020-11-14 11:47 ` Jarmo Hurri 2020-11-14 15:46 ` ian martins 2020-11-15 4:36 ` Jarmo Hurri 2020-11-17 12:07 ` ian martins 2020-12-14 5:55 ` Bastien 2020-11-11 7:45 ` Bastien 2020-10-24 11:58 ` Bastien 2020-10-25 0:30 ` ian martins [this message] 2020-10-28 9:13 ` Bastien 2020-10-31 11:03 ` ian martins
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://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAC=rjb5Q3GZvM+QrJ=NKmffPLsdFyGk04N-db_sHvRFP3Lz6-A@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] ob-java' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.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).