From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about "Creating first patch" guide
Date: Wed, 23 Sep 2015 12:43:46 -0700 [thread overview]
Message-ID: <20150923194346.GA15366@kroah.com> (raw)
In-Reply-To: <CO2PR04MB6033981E5BA07203F744BD5A6440@CO2PR04MB603.namprd04.prod.outlook.com>
On Wed, Sep 23, 2015 at 07:22:08PM +0000, Rob Groner wrote:
> The OutreachyfirstpatchSetup has been very helpful in setting up my computer to
> develop a patch to submit to the kernel overlords.
>
>
>
> I?m at the point where I?ve changed the kernel code, ran and test it, and see
> just my changes with ?git diff?. What has me a little confused is that before
> I actually create the patch file (to submit to the appropriate mailing list),
> it says to actually commit the change. Perhaps I don?t understand how git
> handles commit (I primarily use svn), but it seems like actually committing the
> change is kind of presumptuous before even posting anything on the mailing list
> of those that control the git repository.
>
>
>
> What part am I not understanding?
You should create a branch and work on that, making a commit there, then
it is trivial to turn that into a patch, as the tutorial suggests.
With git, everything can be local, svn requires you to push your changes
to the server, which is the big difference here.
hope this helps,
greg k-h
next prev parent reply other threads:[~2015-09-23 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 19:22 Question about "Creating first patch" guide Rob Groner
2015-09-23 19:43 ` Greg KH [this message]
2015-09-23 20:01 ` Rob Groner
2015-09-23 21:04 ` Greg KH
2015-09-23 21:02 ` Rob Groner
2015-09-24 3:21 ` 慕冬亮
2015-09-24 5:56 ` Karthik Nayak
2015-09-24 6:47 ` 慕冬亮
2015-09-24 6:55 ` Karthik Nayak
2015-09-24 13:07 ` Albino B Neto
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=20150923194346.GA15366@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.