From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: Creating and sending patch without git (Sending As plain text)
Date: Tue, 23 Jul 2013 20:03:11 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1307232200380.2030@localhost6.localdomain6> (raw)
In-Reply-To: <51EEDF14.3010906@gmail.com>
On Wed, 24 Jul 2013, Kumar Gaurav wrote:
> Hi Dan,
>
>
> I have fixed several bugs in a program in staging and now want to send it to
>
> you before sending to maintainers. But currently i don't have git clone of
>
> current kernel. I had downloaded full tarball of 3.11-rc1 version.
>
>
> So please tell me if there's a way to formate a mail and create a path for the
>
> fix that i did. So that you can review my code.
You can read Documentation/SubmittingPatches, compare your results to what
you see on mailing lists, and send your patch to yourself and be sure that
you can save your message as is and apply it.
julia
next prev parent reply other threads:[~2013-07-23 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:53 Creating and sending patch without git (Sending As plain text) Kumar Gaurav
2013-07-23 20:03 ` Julia Lawall [this message]
2013-07-25 11:45 ` Peter Senna Tschudin
2013-07-29 8:28 ` Nicolas Palix
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=alpine.DEB.2.02.1307232200380.2030@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=kernel-janitors@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