All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawn.bohrer@gmail.com (Shawn Bohrer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Git create patch series for multipe commits.
Date: Fri, 26 Sep 2014 13:04:00 -0500	[thread overview]
Message-ID: <20140926180400.GB15362@sbohrermbp13-local.rgmadvisors.com> (raw)
In-Reply-To: <1411752957.63273.YahooMailNeo@web161403.mail.bf1.yahoo.com>

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

  reply	other threads:[~2014-09-26 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  4:54 Git create patch series for multipe commits Anand Moon
2014-09-26 14:18 ` Shawn Bohrer
2014-09-26 17:35   ` Anand Moon
2014-09-26 18:04     ` Shawn Bohrer [this message]
2014-09-26 18:18     ` Valdis.Kletnieks at vt.edu
2014-09-27  8:23 ` Sudip Mukherjee

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=20140926180400.GB15362@sbohrermbp13-local.rgmadvisors.com \
    --to=shawn.bohrer@gmail.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.