mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 0/2] coreutils: Menu maintenance
Date: Wed, 25 Jul 2018 15:18:57 +0200	[thread overview]
Message-ID: <20180725131857.dkfor6ukelrenptq@pengutronix.de> (raw)
In-Reply-To: <6754128.7DkH5cLITu@ada>

Hi,

On Tue, Jul 24, 2018 at 02:38:02PM +0200, Alexander Dahl wrote:
> Am Dienstag, 19. Juni 2018, 15:51:09 CEST schrieb Alexander Dahl:
> > I just stumbled over a vanishing menu entry without comment for the
> > activated busybox tool 'readlink' so I thought I check on more missing
> > comments. One was actually even in the wrong place.
> 
> Maybe the commit message was not clear enough on that? Or should I split that 
> patch in fixing the wrong comment and adding the others?

It just got lost here, sorry. It's in my test queue now and should show up
in master in a few days.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-07-25 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 13:51 Alexander Dahl
2018-06-19 13:51 ` [ptxdist] [PATCH 1/2] coreutils: Fix missing busybox guard comments Alexander Dahl
2018-06-19 13:51 ` [ptxdist] [PATCH 2/2] coreutils: Unify case in comments Alexander Dahl
2018-07-24 12:38 ` [ptxdist] [PATCH 0/2] coreutils: Menu maintenance Alexander Dahl
2018-07-25 13:18   ` Michael Olbrich [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=20180725131857.dkfor6ukelrenptq@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox