Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdbserver: Add .dir-locals.el file
Date: Thu, 05 Mar 2020 16:00:00 -0000	[thread overview]
Message-ID: <0751c6bc-3412-a400-8944-797ed5219918@redhat.com> (raw)
In-Reply-To: <83imjivn4w.fsf@gnu.org>

On 3/5/20 3:26 PM, Eli Zaretskii wrote:
>> Date: Thu, 5 Mar 2020 15:12:32 +0000
>> From: Andrew Burgess <andrew.burgess@embecosm.com>
>> Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
>>
>>>>> Put a single file in the parent directory of those 3, I think.
>>>>
>>>> Good point.  This would affect all projects in the top level,
>>>> though perhaps the file is right for all of them.  
>>>
>>> You can arrange for the settings to affect only some of the
>>> subdirectories, the Emacs manual shows an example of that.
>>
>> I took a look at the examples, and, if I understand correctly I would
>> need to do something like:
> 
> Yes, I think this is correct.

Thanks for exploring this.

> 
>> Given how rarely the .dir-locals files change, my instinct is to just
>> add two new copies, and possibly ensure that all three versions of the
>> file have a big comment saying "remember to update the other versions
>> of this file located in ......".
> 
> I'm okay with that as well, if people prefer it.

Yes, let's do that.

Thanks,
Pedro Alves


  reply	other threads:[~2020-03-05 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  9:53 [PATCH] " Andrew Burgess
2020-03-02 10:17 ` Aktemur, Tankut Baris
2020-03-02 12:31   ` [PATCHv2] " Andrew Burgess
2020-03-02 14:06     ` Pedro Alves
2020-03-02 17:08       ` Andrew Burgess
2020-03-02 17:34         ` Pedro Alves
2020-03-02 17:58           ` Eli Zaretskii
2020-03-02 18:13             ` Pedro Alves
2020-03-02 19:19               ` Eli Zaretskii
     [not found]                 ` <20200305151232.GB3317@embecosm.com>
2020-03-05 15:26                   ` Eli Zaretskii
2020-03-05 16:00                     ` Pedro Alves [this message]
     [not found] ` <BYAPR11MB3030342645BFA8E7610CF862C4E70@BYAPR11MB3030.namprd11.prod.outlook.com>
2020-03-02 12:02   ` [PATCH] " Andrew Burgess
2020-03-02 14:05     ` Pedro Alves

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0751c6bc-3412-a400-8944-797ed5219918@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox