From: Eli Zaretskii <eliz@gnu.org>
To: Orgad Shaneh <orgads@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix cache dir resolving on Windows
Date: Fri, 07 Jun 2019 12:29:00 -0000 [thread overview]
Message-ID: <835zphr33a.fsf@gnu.org> (raw)
In-Reply-To: <CAGHpTB+Y+kO=ZiKtTft3yG4mMR+27DYfqJGQWBLvu=VKCgRyLw@mail.gmail.com> (message from Orgad Shaneh on Fri, 7 Jun 2019 11:58:45 +0300)
> From: Orgad Shaneh <orgads@gmail.com>
> Date: Fri, 7 Jun 2019 11:58:45 +0300
>
> On Fri, Jun 7, 2019 at 11:01 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > Actually, I see that we mention HOME on Windows in the manual, in a
> > footnote that's part of the "Startup" node. I think we should
> > document this addition there. Would you like to add a change to the
> > manual as well?
>
> This refers to gdbinit, which probably should also be added a fallback
> to APPDATA. Anyway, it is not related to this patch, which is about
> the cache directory.
Oh, so we probe $HOME in more than one place? Yes, I think we should
do this in all of those places, preferably through a single function.
> > P.S. I see that you don't have a copyright assignment on file, which
> > means we are limited in the amount of changes we can accept from you.
> > Would you like to start the legal paperwork of assigning to the FSF
> > the copyright for your changes? If so, I will send you the form to
> > fill.
>
> Sure.
Thanks, form sent off-list.
next prev parent reply other threads:[~2019-06-07 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 19:37 orgads
2019-06-04 14:44 ` Eli Zaretskii
2019-06-04 15:06 ` Simon Marchi
2019-06-04 16:17 ` Eli Zaretskii
2019-06-07 6:21 ` orgads
2019-06-07 6:23 ` Orgad Shaneh
2019-06-07 6:27 ` Eli Zaretskii
2019-06-07 6:27 ` orgads
2019-06-07 7:36 ` Eli Zaretskii
2019-06-07 8:01 ` Eli Zaretskii
[not found] ` <CAGHpTB+Y+kO=ZiKtTft3yG4mMR+27DYfqJGQWBLvu=VKCgRyLw@mail.gmail.com>
2019-06-07 12:29 ` Eli Zaretskii [this message]
2019-06-07 18:10 ` Tom Tromey
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=835zphr33a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=orgads@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox