public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Removal of client175
Date: Sat, 09 Oct 2021 13:28:51 +0100	[thread overview]
Message-ID: <23C10F30-9E0F-4C6C-87B0-1E94997CCE2F@ipfire.org> (raw)
In-Reply-To: <8728c93b-f7e0-43a4-6351-efb74787165c@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

Hello Adolf,

> On 6 Oct 2021, at 15:32, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I am getting ready to create the patch for the removal of client175.


Thank you for taking care of this.

> However it is not clear to me what the relationship is between client175 and mpfire/mpd/mpc. Can mpfire/mpd/mpc work and be used without client175 being present or are they linked, in which case presumably they should also be removed then?

mpd/mpc are standalone and client175 is just a WUI for them. Technically they can stay.

If we want them to stay is another question, but for the time being I would say yes.

-Michael

> 
> Thanks for your advice.
> 
> Adolf.
> 


      reply	other threads:[~2021-10-09 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 14:32 Adolf Belka
2021-10-09 12:28 ` Michael Tremer [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=23C10F30-9E0F-4C6C-87B0-1E94997CCE2F@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox