All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Transaction commit: none (default)
Date: Mon, 16 Jun 2014 07:06:08 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.06.16.07.06.08@googlemail.com> (raw)
In-Reply-To: 20140616014739.GB19071@merlins.org

On Sun, 15 Jun 2014 18:47:39 -0700, Marc MERLIN wrote:

> On Mon, Jun 16, 2014 at 09:35:23AM +0800, Wang Shilong wrote:
>> On 06/15/2014 12:05 AM, Marc MERLIN wrote:
>> >Taking snapshots is now output this in addition of the snapshot
>> >operation.
>> >
>> >Transaction commit: none (default)
>> >
>> >1) Is that expected/normal? It looks kind of spamming/useless to me?
>> >2) If it's useful, what's the use I'm not getting?
>> Addressed a issue that subvolumes reappear after deletetion if poweroff
>> happen.
>> 
>> http://www.spinics.net/lists/linux-btrfs/msg29547.html
> 
> I see, thank you for the pointer.
> In the case of my script, it's console spam that I wish I could make go
> away, but grep -v will do that for me :)
> 
> If it annoys other people, maybe having a -q (quiet) that removes this
> message would be useful?

IMHO it should be the reverse: be quiet by default and require -v, just 
as more explicit behaviour also requires additional options.
With default options I expect default behaviour. Telling me that the 
default behaviour happened is just noise.

cheers
Holger


  reply	other threads:[~2014-06-16  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 16:05 Transaction commit: none (default) Marc MERLIN
2014-06-16  1:35 ` Wang Shilong
2014-06-16  1:47   ` Marc MERLIN
2014-06-16  7:06     ` Holger Hoffstätte [this message]
2014-06-16  7:09       ` Wang Shilong
2014-06-18 14:19         ` David Sterba
2014-06-18 14:42           ` Marc MERLIN
2014-06-17 18:15       ` Marc MERLIN

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=pan.2014.06.16.07.06.08@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=linux-btrfs@vger.kernel.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.