From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] HACKING: document where to send patches
Date: Wed, 05 Mar 2014 10:21:54 +0900 [thread overview]
Message-ID: <1393982514.3870.5.camel@kjgkr> (raw)
In-Reply-To: <1393937715-30399-1-git-send-email-ncopa@alpinelinux.org>
Hi,
This information can be retrieved from:
linux/MAINTAINERS.
No need to do this.
Thanks,
2014-03-04 (화), 12:55 +0000, Natanael Copa:
> Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
> ---
> HACKING | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 HACKING
>
> diff --git a/HACKING b/HACKING
> new file mode 100644
> index 0000000..515b73e
> --- /dev/null
> +++ b/HACKING
> @@ -0,0 +1 @@
> +Send patches to linux-f2fs-devel@lists.sourceforge.net
--
Jaegeuk Kim
Samsung
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2014-03-05 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 12:55 [PATCH] HACKING: document where to send patches Natanael Copa
2014-03-05 1:21 ` Jaegeuk Kim [this message]
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=1393982514.3870.5.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=ncopa@alpinelinux.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;
as well as URLs for NNTP newsgroup(s).