From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: Add f2fs bug tracker link
Date: Mon, 28 Nov 2022 14:02:02 -0800 [thread overview]
Message-ID: <Y4Uv2tuHerLvJdLl@google.com> (raw)
In-Reply-To: <20221128035150.30787-1-frank.li@vivo.com>
If you don't mind, let me merge this patch into Chao's patch, since both
are same topic.
On 11/28, Yangtao Li wrote:
> It's better to use bugzilla.kernel.org for reporting bugs.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> Documentation/filesystems/f2fs.rst | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
> index 6e67c5e6c7c3..67e1f3e86f32 100644
> --- a/Documentation/filesystems/f2fs.rst
> +++ b/Documentation/filesystems/f2fs.rst
> @@ -25,10 +25,14 @@ a consistency checking tool (fsck.f2fs), and a debugging tool (dump.f2fs).
>
> - git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
>
> -For reporting bugs and sending patches, please use the following mailing list:
> +For sending patches, please use the following mailing list:
>
> - linux-f2fs-devel@lists.sourceforge.net
>
> +For reporting bugs, please use the following f2fs bug tracker link:
> +
> +- https://bugzilla.kernel.org/enter_bug.cgi?product=File%20System&component=f2fs
> +
> Background and Design issues
> ============================
>
> --
> 2.25.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: Add f2fs bug tracker link
Date: Mon, 28 Nov 2022 14:02:02 -0800 [thread overview]
Message-ID: <Y4Uv2tuHerLvJdLl@google.com> (raw)
In-Reply-To: <20221128035150.30787-1-frank.li@vivo.com>
If you don't mind, let me merge this patch into Chao's patch, since both
are same topic.
On 11/28, Yangtao Li wrote:
> It's better to use bugzilla.kernel.org for reporting bugs.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> Documentation/filesystems/f2fs.rst | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
> index 6e67c5e6c7c3..67e1f3e86f32 100644
> --- a/Documentation/filesystems/f2fs.rst
> +++ b/Documentation/filesystems/f2fs.rst
> @@ -25,10 +25,14 @@ a consistency checking tool (fsck.f2fs), and a debugging tool (dump.f2fs).
>
> - git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
>
> -For reporting bugs and sending patches, please use the following mailing list:
> +For sending patches, please use the following mailing list:
>
> - linux-f2fs-devel@lists.sourceforge.net
>
> +For reporting bugs, please use the following f2fs bug tracker link:
> +
> +- https://bugzilla.kernel.org/enter_bug.cgi?product=File%20System&component=f2fs
> +
> Background and Design issues
> ============================
>
> --
> 2.25.1
next prev parent reply other threads:[~2022-11-28 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 3:51 [f2fs-dev] [PATCH] f2fs: Add f2fs bug tracker link Yangtao Li via Linux-f2fs-devel
2022-11-28 3:51 ` Yangtao Li
2022-11-28 22:02 ` Jaegeuk Kim [this message]
2022-11-28 22:02 ` Jaegeuk Kim
2022-11-29 4:18 ` [f2fs-dev] " Yangtao Li via Linux-f2fs-devel
2022-11-29 4:18 ` Yangtao Li
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=Y4Uv2tuHerLvJdLl@google.com \
--to=jaegeuk@kernel.org \
--cc=frank.li@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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.