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: vnstat 2.6 - (was: Re: [PATCH] tmux: Update to 3.1)
Date: Mon, 27 Apr 2020 13:13:41 +0100	[thread overview]
Message-ID: <0CD1DE90-D72E-4063-893B-DDC8132B4CF2@ipfire.org> (raw)
In-Reply-To: <892cf7c4-b206-4fa4-6188-16f748f53767@ipfire.org>

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

Hi,

> On 25 Apr 2020, at 12:26, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 25.04.2020 10:07, Michael Tremer wrote:
>> Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
>> 
>> Thank you!
>> 
>> -Michael
>> 
>>> ...
> 
> No problem - it just came my way... ;-)
> 
> Besides: I'm thinking about the (8?) update patches for 'vnstatn 2.6'.
> 
> These are quite a few, because - as you know - it took me some time to
> get the initscript right. And one commit
> (https://patchwork.ipfire.org/patch/2936/) even has the wrong subject.
> 
> Nevertheless, its running without problems since then. Today I deleted
> the no longer needed files from '/var/log/vnstat/' ('.blue0', '.green0',
> '.red0'). The new file, 'vnstat.db' takes about 250KB at the moment and
> is staying there.

It is best if you write these things as a response to the original patch, because they will then appear in the history of patchwork.

But in general, I would recommend that this is being merged into next and we test it with more users.

> But: should I send a new patch series for this update?

Why? To clean up the mess? I would leave this for Arne. If he can work it out then not. Otherwise, a new patch series is probably the easier.

Best,
-Michael

> 
> Best,
> 
> Matthias


       reply	other threads:[~2020-04-27 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <892cf7c4-b206-4fa4-6188-16f748f53767@ipfire.org>
2020-04-27 12:13 ` Michael Tremer [this message]
2020-04-29 18:06   ` vnstat 2.6 - 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=0CD1DE90-D72E-4063-893B-DDC8132B4CF2@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