From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Christian Biesinger <cbiesinger@google.com>,
Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>,
help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Wed, 15 Jan 2020 02:34:00 -0000 [thread overview]
Message-ID: <4840dec1-747c-e458-9dd8-1fb89fb15866@gotplt.org> (raw)
In-Reply-To: <CAPTJ0XEmDFBSRhabGx6YoM=R8H9YxxY3tsc1i6Mi_=Eg_fcq6g@mail.gmail.com>
On 15/01/20 12:35 am, Christian Biesinger wrote:
> Any news on this upgrade? Would be nice to play with patchwork for gdb.
>
Sorry I got caught up in other work and had to put this aside. I hope
to resume in a week or so.
Siddhesh
prev parent reply other threads:[~2020-01-15 2:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 5:01 Siddhesh Poyarekar
2019-11-28 5:11 ` Simon Marchi
2019-11-28 5:25 ` Maciej W. Rozycki
2019-11-28 5:47 ` Siddhesh Poyarekar
2019-11-28 15:47 ` Carlos O'Donell
2019-11-30 11:35 ` Maciej W. Rozycki
2019-12-01 4:35 ` Siddhesh Poyarekar
2019-12-01 16:27 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:06 ` Carlos O'Donell
2019-11-28 15:45 ` Carlos O'Donell
2019-11-28 16:03 ` Florian Weimer
2019-11-28 16:09 ` Siddhesh Poyarekar
2019-11-28 16:24 ` Florian Weimer
2019-11-29 12:52 ` Andrew Burgess
2019-11-29 13:24 ` Florian Weimer
2019-11-28 16:24 ` Carlos O'Donell
2019-11-28 16:45 ` Siddhesh Poyarekar
2019-12-08 12:07 ` Siddhesh Poyarekar
2019-12-08 12:10 ` Florian Weimer
2019-12-08 12:21 ` Christian Brauner
2019-12-09 7:56 ` Siddhesh Poyarekar
2019-12-09 16:52 ` Konstantin Ryabitsev
2019-12-09 17:00 ` Siddhesh Poyarekar
2019-12-09 15:44 ` Sergio Durigan Junior
2019-12-09 16:57 ` Siddhesh Poyarekar
2019-12-09 17:15 ` Sergio Durigan Junior
2020-01-14 19:06 ` Christian Biesinger
2020-01-15 2:34 ` Siddhesh Poyarekar [this message]
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=4840dec1-747c-e458-9dd8-1fb89fb15866@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=help-guix@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).