From: Jim Porter <jporterbugs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Fix M-x gdb when debugging over Tramp
Date: Thu, 15 Apr 2021 22:03:10 -0700 [thread overview]
Message-ID: <CANh=_JF98WrGHGttcVMZDq3EPOkV5TCcce-UWF2mWAXQtR7NLA@mail.gmail.com> (raw)
In-Reply-To: <8735vs6kyd.fsf@gmx.de>
On Thu, Apr 15, 2021 at 12:55 AM Michael Albinus <michael.albinus@gmx.de> wrote:
> Jim Porter <jporterbugs@gmail.com> writes:
> >> I have also the impression that this is related to bug#39408, bug#28392
> >> and bug#44151. Perhaps this could be checked, and in case of yes, I
> >> would much appreciate if we could solve all of these bugs.
> >
> > Indeed, it looks like bug#39408 is my issue (1) above, and bug#28392
> > is my issue (2). bug#44151 looks like it's done(ish): the first part
> > is something you've already fixed in Tramp, and the second part
> > (mentioned in comment 11) is a duplicate of bug#28392.
>
> That's why bug#28392 and bug#44151 are merged :-)
Right, just making sure we were on the same page. :)
> > Given that these are already tracked as bugs, should I just submit
> > patches to both bug#39408 and bug#28392? I'd have to rearrange my
> > existing patches slightly, but that's easy.
>
> Yes, please do. And since nobody else has reacted to these bugs for
> years, I'm in the mood to commit your patches as soon as your paperwork
> with FSF is fixed. Unless somebody comments until.
Ok, I submitted the patches to the corresponding bugs.
Thanks,
- Jim
next prev parent reply other threads:[~2021-04-16 5:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 23:14 [PATCH] Fix M-x gdb when debugging over Tramp Jim Porter
2021-04-08 12:58 ` Michael Albinus
2021-04-15 5:02 ` Jim Porter
2021-04-15 7:55 ` Michael Albinus
2021-04-16 5:03 ` Jim Porter [this message]
2021-05-01 4:13 ` Jim Porter
2021-05-01 10:18 ` Michael Albinus
2021-04-19 11:55 ` William Xu
2021-04-19 12:44 ` Michael Albinus
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='CANh=_JF98WrGHGttcVMZDq3EPOkV5TCcce-UWF2mWAXQtR7NLA@mail.gmail.com' \
--to=jporterbugs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.