All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Henriksson <andreas@fatal.se>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] patches submitted downstream (Debian)
Date: Wed, 3 Oct 2018 15:44:01 +0200	[thread overview]
Message-ID: <20181003134401.nomhxbymjqcr2cxh@fatal.se> (raw)
In-Reply-To: <20181002210424.GJ3219@comp-core-i7-2640m-0182e6>

On Tue, Oct 02, 2018 at 11:04:24PM +0200, Alexey Gladkov wrote:
> On Wed, May 30, 2018 at 08:03:47PM +0200, Andreas Henriksson wrote:
> > Hello,
> > 
> > A couple of patches improving manpages has recently been submitted
> > downstream. Please consider applying the upstream. See:
> > 
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=kbd&tag=patch
> > 
> > (As you can see there's also a third patch which has been sitting for a
> > long time so not sure about its usefulness. If you look at it your
> > conclusion about it would be appreciated none the less.)
> 
> Can you send a patch or pull-request here ?

I'm sorry I failed to resolve the conflicts when trying to apply the
patches on top of git master. I really don't want to be the middle
man here either. I've already asked Bjarni to submit the patches himself
but if there's no interest on either side to go the extra mile, then
I'll stay out of this and lets just let the patches rot. Sorry to not
be more helpful.

Regards,
Andreas Henriksson


      reply	other threads:[~2018-10-03 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 18:03 [kbd] patches submitted downstream (Debian) Andreas Henriksson
2018-10-02 21:04 ` Alexey Gladkov
2018-10-03 13:44   ` Andreas Henriksson [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=20181003134401.nomhxbymjqcr2cxh@fatal.se \
    --to=andreas@fatal.se \
    --cc=gladkov.alexey@gmail.com \
    --cc=kbd@lists.altlinux.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 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.