public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Revived as addon: squid graphs 3.2
Date: Sun, 12 Nov 2017 11:11:14 +0100	[thread overview]
Message-ID: <ef2e7999-3ee9-2fd0-06e2-4a8a4c6bf94b@ipfire.org> (raw)
In-Reply-To: <20171112003456.10198-1-matthias.fischer@ipfire.org>

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

Hi,

On 12.11.2017 01:34, Matthias Fischer wrote:
> Hi,
> 
> For details see:
> https://sourceforge.net/projects/squid-graph/
> ...

Ok guys - sorry for the noise, but currently I'm not so fit as I'd like
to be (flu).

After looking at my upload results in patchwork and GIT and - for
example - thinking about future updates I decided to rework this addon
from scratch. So for now I'll change this to 'under review' in patchwork.

Reasons for this:
During testing its installing and working ok, BUT(!)...

Publishing or merging 'squid-graph' the way I did would induce the need
to pack and upload a NEW archive every time something gets changed. Be
it a language-file or some script or some GUI-file or something else.

After looking at this, I thought it would be better and easier to
maintain this addon if I build and pack it like 'squid-accounting' or
'wio' (e.g.).

Again: sorry for the noise - I'm working on it.

Best,
Matthias

  reply	other threads:[~2017-11-12 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12  0:34 Matthias Fischer
2017-11-12 10:11 ` Matthias Fischer [this message]
2017-11-13 22:56   ` Michael Tremer
2017-11-14 11:48     ` Matthias Fischer
2017-11-15 13:17     ` Matthias Fischer
  -- strict thread matches above, loose matches on Subject: below --
2017-11-12 20:59 [PATCH] Revived (as addon): " Matthias Fischer
2017-11-11 21:45 Matthias Fischer
2017-11-11 22:38 ` Matthias Fischer

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=ef2e7999-3ee9-2fd0-06e2-4a8a4c6bf94b@ipfire.org \
    --to=matthias.fischer@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