From mboxrd@z Thu Jan  1 00:00:00 1970
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
Date: Fri, 26 Sep 2014 14:18:41 -0400
Subject: Git create patch series for multipe commits.
In-Reply-To: Your message of "Fri, 26 Sep 2014 10:35:57 -0700."
	<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: <11419.1411755521@turing-police.cc.vt.edu>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Fri, 26 Sep 2014 10:35:57 -0700, Anand Moon said:

> 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.

Each patch should do exactly one thing. So if you find 3 different issues that
need fixing in foo.c, that should result in 3 commits and 3 patches.  Those 3
may or may not be related enough to require a patch series (where all the
patches should be related).  However, there's a special case where the commits
are close enough together to cause conflicts and/or bisection issues if applied
in the wrong order.  Those should be in a series so they get applied in order
and avoid the conflict/bisection issue.

Hope that helps...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140926/bf9f9238/attachment.bin