From mboxrd@z Thu Jan  1 00:00:00 1970
From: shawn.bohrer@gmail.com (Shawn Bohrer)
Date: Fri, 26 Sep 2014 13:04:00 -0500
Subject: Git create patch series for multipe commits.
In-Reply-To: <1411752957.63273.YahooMailNeo@web161403.mail.bf1.yahoo.com>
References: <1411707265.57564.YahooMailNeo@web161404.mail.bf1.yahoo.com>
	<20140926141810.GA15362@sbohrermbp13-local.rgmadvisors.com>
	<1411752957.63273.YahooMailNeo@web161403.mail.bf1.yahoo.com>
Message-ID: <20140926180400.GB15362@sbohrermbp13-local.rgmadvisors.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Fri, Sep 26, 2014 at 10:35:57AM -0700, Anand Moon wrote:
> Hi Shawn,
> 
> Thanks I will give it a try.
> 
> One more question, if the change belong to single file
> and we are fixing multiple issue we need to different commit
> for each changes. And then club them into patch series.
> Am I right.

I'm not sure if I understand the question or not.  If you need to fix
multiple issues that are all in the same source file but those fixes
are corrections to several different patches in your series, then yes
you should make a single new commit for each fix.  Then with 'git
rebase -i' you can roll each fix back into the correct patch.

If all of the fixes are going to be rolled back into a single patch
then you can simply make a single new commit and roll that back into
the correct patch with 'git rebase -i'.

If you are not familiar with 'git rebase -i' you should read the
"INTERACTIVE MODE" section in the man page 'git help rebase'.  It is an
amazingly powerful tool.

Oh, and I probably should have mentioned it in my first response.  But
if you've never sent a patch before it is a good idea to try sending
it to yourself first.  You can apply the patches to a new branch with
'git am'.

--
Shawn