From: Eli Zaretskii <eliz@gnu.org>
To: Elijah G <eg642616@gmail.com>
Cc: sbaugh@catern.com, sbaugh@janestreet.com, philipk@posteo.net,
emacs-devel@gnu.org, luangruo@yahoo.com
Subject: Re: [PATCH] Flymake Support Indicator Errors in Margin
Date: Thu, 18 Apr 2024 12:10:02 +0300 [thread overview]
Message-ID: <864jbzf34l.fsf@gnu.org> (raw)
In-Reply-To: <CACnP4NKutuS=-=+6RL2mLu24mOX1Hp5FvxxVjQbMVtT4eU4dhQ@mail.gmail.com> (message from Elijah G on Sun, 7 Apr 2024 11:20:41 -0600)
> From: Elijah G <eg642616@gmail.com>
> Date: Sun, 7 Apr 2024 11:20:41 -0600
> Cc: sbaugh@catern.com, sbaugh@janestreet.com, philipk@posteo.net,
> emacs-devel@gnu.org, luangruo@yahoo.com
>
> On Sat, Apr 6, 2024 at 11:48 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > From: Elijah G <eg642616@gmail.com>
> > > Date: Sat, 6 Apr 2024 14:14:34 -0600
> > > Cc: sbaugh@catern.com, sbaugh@janestreet.com, philipk@posteo.net,
> > > emacs-devel@gnu.org, luangruo@yahoo.com
> > >
> > > > Last, but not least: please mention this change (and the new user
> > > > options) in NEWS and in the Flymake manual.
> > >
> > > Thank you, I've now fixed the patch and documented the changes done.
> >
> > See below for some additional comments.
>
> Thank you, I've now fixed the patch.
> Sorry if this is the second time I fixed the patch,
> I'm not good at documenting code.
>
> > > Also I have a question, Do I need to assign copyright each time
> > > that I want to contribute to Flymake?
> >
> > No, you assign the copyright for past and future changes, and you do
> > it only once.
> >
> > Did you start the paperwork already? I don't see your assignment on
> > file, so if you haven't started the paperwork, now is the time to do
> > it. Let me know if you need me to send you the form to fill and the
> > instructions, to start the paperwork.
>
> Thanks, I've already signed the paperwork and sent to assign@gnu.org,
> however i didn't get any response, i'm not sure if i wrote the subject well
> in the email, Can you help me how I should send my signed paperwork
> off-list?
>
> Thanks.
Thank you, I have now installed this on the master branch.
next prev parent reply other threads:[~2024-04-18 9:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 23:18 [PATCH] Flymake Support Indicator Errors in Margin Elijah G
2024-03-12 9:24 ` Philip Kaludercic
2024-03-12 17:22 ` Elijah G
2024-03-13 12:18 ` Eli Zaretskii
2024-03-14 1:50 ` Elijah G
2024-03-14 11:05 ` Eli Zaretskii
2024-03-14 11:28 ` João Távora
2024-03-14 15:35 ` Elijah G
2024-03-16 11:10 ` Eli Zaretskii
2024-03-17 16:44 ` bird
2024-03-17 17:01 ` Eli Zaretskii
2024-03-17 17:34 ` Elijah G
2024-03-17 18:43 ` bird
2024-03-17 19:21 ` Elijah G
2024-03-25 1:46 ` Elijah G
2024-03-27 0:13 ` sbaugh
2024-03-27 0:36 ` Elijah G
2024-03-27 21:29 ` Elijah G
2024-03-28 6:01 ` Eli Zaretskii
2024-03-28 17:34 ` Elijah G
2024-04-06 11:36 ` Eli Zaretskii
2024-03-28 7:30 ` Juri Linkov
2024-03-28 17:44 ` Elijah G
2024-04-06 11:35 ` Eli Zaretskii
2024-04-06 20:14 ` Elijah G
2024-04-07 5:47 ` Eli Zaretskii
2024-04-07 17:20 ` Elijah G
2024-04-18 9:10 ` Eli Zaretskii [this message]
2024-03-19 7:03 ` Augusto Stoffel
2024-03-17 17:49 ` Elijah G
2024-03-19 7:04 ` Augusto Stoffel
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864jbzf34l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eg642616@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=philipk@posteo.net \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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://git.savannah.gnu.org/cgit/emacs.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).