From: Neil Roberts <bpeeluk@yahoo.co.uk>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33400@debbugs.gnu.org
Subject: bug#33400: [PATCH] Let dir locals for more specific modes override those from less
Date: Wed, 08 May 2019 09:18:45 +0200 [thread overview]
Message-ID: <87mujxxvl6.fsf@yahoo.co.uk> (raw)
In-Reply-To: <87v9yzpbls.fsf@gmail.com>
Noam Postavsky <npostavs@gmail.com> writes:
> This patch looks basically good to me (some minor formatting:
> sentences should end in double space, and the commit message misses a
> ChangeLog formatted entry), but it exceeds to copyright exemption
> limit. Would you be willing to sign papers?
Apparently my assignment/disclaimer process is complete. I sent a v2 of
the patch which I think addresses the issues you mentioned and also adds
documentation to the manual. I got confused by the complicated bug
tracking system and it ended up as a new bug (#35522).
Regards,
- Neil
next prev parent reply other threads:[~2019-05-08 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 13:21 bug#33400: 26.1; Order changed for overriding “nil” mode in dir-locals Neil Roberts
2018-11-15 18:01 ` bug#33400: [PATCH] Let dir locals for more specific modes override those from less Neil Roberts
2019-04-27 18:05 ` Noam Postavsky
2019-04-29 7:45 ` Neil Roberts
2019-04-29 14:41 ` Eli Zaretskii
2019-04-29 12:58 ` Michael Albinus
2019-05-08 7:18 ` Neil Roberts [this message]
2019-05-10 1:30 ` Noam Postavsky
2019-05-10 6:44 ` Eli Zaretskii
2019-05-10 10:57 ` bug#33400: [PATCH v3] " Neil Roberts
2019-05-12 14:03 ` Noam Postavsky
2019-05-01 11:49 ` bug#35522: [PATCH v2] " Neil Roberts
2018-11-16 9:48 ` bug#33400: 26.1; Order changed for overriding “nil” mode in dir-locals Phil Sainty
2019-04-25 17:08 ` bug#33400: BUMP: please merge the fix for this bug Mark Janes
2019-04-26 17:46 ` bug#33400: Merge with bug#30008? Kévin Le Gouguec
2019-04-27 18:06 ` Noam Postavsky
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=87mujxxvl6.fsf@yahoo.co.uk \
--to=bpeeluk@yahoo.co.uk \
--cc=33400@debbugs.gnu.org \
--cc=npostavs@gmail.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).