From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: anticrisisg@gmail.com, 44834@debbugs.gnu.org, rms@gnu.org,
dgutov@yandex.ru
Subject: bug#44834: Fix for failing indentation of Tcl procs nested in namespace
Date: Tue, 09 Feb 2021 17:40:50 +0200 [thread overview]
Message-ID: <8335y5l059.fsf@gnu.org> (raw)
In-Reply-To: <87h7mlk5re.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 09 Feb 2021 09:24:53 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 09 Feb 2021 09:24:53 +0100
> Cc: anticrisisg@gmail.com, 44834@debbugs.gnu.org, dgutov@yandex.ru
>
> Richard Stallman <rms@gnu.org> writes:
>
> > but that is not entirely correct either. People could misinterpret
> > what is "trivial."
> >
> > Please put in
> >
> > about 10 new or modified nontrivial lines of code. (A line with
> > a symbol is nontrivial.)
>
> Eli has changed the text further; please have a look.
FTR, the text now says:
Once the cumulative amount of your submissions exceeds about 15 lines
of non-trivial code you added or changed (not counting deleted lines),
we will need you to assign to the FSF the copyright for your
contributions. Ask on emacs-devel@gnu.org, and we will send you the
necessary form together with the instructions to fill and email it, in
order to start this legal paperwork.
next prev parent reply other threads:[~2021-02-09 15:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 23:58 bug#44834: 27.1; Tcl mode enforces bad indentation following proc within a namespace Morgan Willcock
2021-01-08 22:21 ` bug#44834: change severity Anticrisis
2021-01-08 23:04 ` bug#44834: Patch to provide failing test for bug 44834 Anticrisis
2021-01-09 1:24 ` Anticrisis
2021-01-10 12:10 ` Lars Ingebrigtsen
2021-01-10 18:41 ` Anticrisis
2021-01-11 15:17 ` Lars Ingebrigtsen
2021-01-22 1:17 ` bug#44834: Fix for failing indentation of Tcl procs nested in namespace Anticrisis
2021-01-27 4:37 ` Lars Ingebrigtsen
2021-02-06 21:51 ` Anticrisis
2021-02-07 5:47 ` Richard Stallman
2021-02-07 7:26 ` Anticrisis
2021-02-06 22:55 ` Dmitry Gutov
2021-02-07 5:47 ` Richard Stallman
2021-02-07 11:40 ` Lars Ingebrigtsen
2021-02-08 3:44 ` Richard Stallman
2021-02-08 6:30 ` Lars Ingebrigtsen
2021-02-09 6:07 ` Richard Stallman
2021-02-09 8:24 ` Lars Ingebrigtsen
2021-02-09 15:40 ` Eli Zaretskii [this message]
2021-02-10 5:32 ` Richard Stallman
2021-02-10 15:08 ` Eli Zaretskii
2021-02-11 13:39 ` Richard Stallman
2021-02-11 14:00 ` Lars Ingebrigtsen
2021-02-11 14:39 ` Eli Zaretskii
2021-02-12 5:48 ` Richard Stallman
2021-02-12 5:48 ` Richard Stallman
2021-02-12 7:26 ` Eli Zaretskii
2021-02-12 8:14 ` Lars Ingebrigtsen
2021-02-12 11:16 ` Eli Zaretskii
2021-02-13 3:26 ` Richard Stallman
2021-02-13 11:37 ` Lars Ingebrigtsen
2021-02-13 12:25 ` Dmitry Gutov
2021-02-16 5:19 ` Richard Stallman
2021-02-16 12:05 ` Dmitry Gutov
2021-02-16 12:06 ` Lars Ingebrigtsen
2021-02-16 15:38 ` Eli Zaretskii
2021-02-16 16:29 ` Lars Ingebrigtsen
2021-02-16 17:15 ` Juri Linkov
2021-02-16 18:53 ` Eli Zaretskii
2021-02-18 6:12 ` Richard Stallman
2021-02-18 14:08 ` Eli Zaretskii
2021-02-18 14:15 ` Dmitry Gutov
2021-02-17 4:12 ` Richard Stallman
2021-02-10 15:24 ` Lars Ingebrigtsen
2021-02-10 16:03 ` Matt Armstrong
2021-02-11 13:39 ` Richard Stallman
2021-02-11 14:41 ` Eli Zaretskii
2021-02-11 14:49 ` Dmitry Gutov
2021-02-12 5:48 ` Richard Stallman
2021-01-22 19:37 ` bug#44834: Patch also closes bug#44083 Anticrisis
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=8335y5l059.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44834@debbugs.gnu.org \
--cc=anticrisisg@gmail.com \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=rms@gnu.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.
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).