Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: David Sterba <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: mkfs: remove experimental tag
Date: Fri, 1 Aug 2014 12:16:22 +0900	[thread overview]
Message-ID: <53DB0686.8020208@jp.fujitsu.com> (raw)
In-Reply-To: <1406809294-24702-1-git-send-email-dsterba@suse.cz>

(2014/07/31 21:21), David Sterba wrote:
> Make it consistent with kernel status and documentation.
> 
> Signed-off-by: David Sterba <dsterba@suse.cz>

Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>

I'm glad to see this patch :-)

Thanks,
Satoru

> ---
>   mkfs.c | 5 ++---
>   1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/mkfs.c b/mkfs.c
> index 16e92221a547..538b6e6837b2 100644
> --- a/mkfs.c
> +++ b/mkfs.c
> @@ -1439,8 +1439,8 @@ int main(int ac, char **av)
>   	}
>   
>   	/* if we are here that means all devs are good to btrfsify */
> -	printf("\nWARNING! - %s IS EXPERIMENTAL\n", BTRFS_BUILD_VERSION);
> -	printf("WARNING! - see http://btrfs.wiki.kernel.org before using\n\n");
> +	printf("%s\n", BTRFS_BUILD_VERSION);
> +	printf("See http://btrfs.wiki.kernel.org for more\n\n");
>   
>   	dev_cnt--;
>   
> @@ -1597,7 +1597,6 @@ raid_groups:
>   	    label, first_file, nodesize, leafsize, sectorsize,
>   	    pretty_size(btrfs_super_total_bytes(root->fs_info->super_copy)));
>   
> -	printf("%s\n", BTRFS_BUILD_VERSION);
>   	btrfs_commit_transaction(trans, root);
>   
>   	if (source_dir_set) {
> 


  reply	other threads:[~2014-08-01  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 12:21 [PATCH] btrfs-progs: mkfs: remove experimental tag David Sterba
2014-08-01  3:16 ` Satoru Takeuchi [this message]
2014-08-01 16:38 ` Kyle Gates
2014-08-01 16:50   ` David Sterba

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=53DB0686.8020208@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=dsterba@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox