public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Svante Signell <svante.signell@gmail.com>
To: "Héctor Orón Martínez" <hector.oron@gmail.com>, 881569@bugs.debian.org
Cc: bug-hurd@gnu.org, gdb-patches@sourceware.org, thomas@codesourcery.com
Subject: Re: Bug#881569: [Fwd: gdb: FTBFS on hurd-i386]
Date: Sun, 07 Jan 2018 23:11:00 -0000	[thread overview]
Message-ID: <1515366658.3297.0.camel@gmail.com> (raw)
In-Reply-To: <1514414208.21764.5.camel@gmail.com>

Ping

On Wed, 2017-12-27 at 23:36 +0100, Svante Signell wrote:
> On Tue, 2017-12-26 at 09:40 +0100, Héctor Orón Martínez wrote:
> > Hello Svante,
> > 
> > On Sat, Dec 23, 2017 at 7:41 PM, Svante Signell
> > <svante.signell@gmail.com> wrote:
> > > Hello,
> > > 
> > > These patches was submitted to Debian November 13 2017. Nothing has
> > > happened so far, so maybe upstream would be interested to consider
> > > the
> > > patches for next release.
> > 
> > I would like to have them applied in Debian package for next release,
> > however it is taking more time than I thought, then I am going on
> > vacations. If you are able to upload to Debian, feel free to NMU the
> > package, otherwise, I'll try to have a look in a couple weeks.
> 
> Hi again,
> 
> Unfortunately I'm not authorized to NMU that package. However, the
> reason for submitting the patches upstream is that they should be
> applied there. In the meanwhile we could create a Debian package of
> 8.0.1 (or later). If you don't have time maybe Samuel could help out
> here?
> 
> Thanks for your reply anyway!

      reply	other threads:[~2018-01-07 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1510543894.5221.5.camel@gmail.com>
2017-12-23 18:39 ` Svante Signell
2017-12-26  8:40   ` Bug#881569: " Héctor Orón Martínez
2017-12-27 22:36     ` Svante Signell
2018-01-07 23:11       ` Svante Signell [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=1515366658.3297.0.camel@gmail.com \
    --to=svante.signell@gmail.com \
    --cc=881569@bugs.debian.org \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hector.oron@gmail.com \
    --cc=thomas@codesourcery.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).