From: Alison Schofield <amsfield22@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] patchset question
Date: Wed, 21 Oct 2015 10:18:12 -0700 [thread overview]
Message-ID: <20151021171811.GA16768@Ubuntu-D830> (raw)
In-Reply-To: <alpine.DEB.2.02.1510210723340.2038@localhost6.localdomain6>
On Wed, Oct 21, 2015 at 07:24:15AM +0200, Julia Lawall wrote:
> On Tue, 20 Oct 2015, Alison Schofield wrote:
>
> >
> > Patchset help needed:
> >
> > I've changed one file in 5 different ways..all cleanup related.
> > It will be split into 5 patches.
> >
> > In one branch I used git add -pi followed by commit to incrementally
> > create 5 commits. Each one dependent on the previous. This is easy to grab
> > and build as a patchset because they are all on the same branch.
> >
> > Is this method OK?
> >
> > (The alternative is to give each commit it's own branch to keep them
> > independent.)
> >
> > Searching archives of opw kernel I found reference to the dependent
> > commits, stating it was OK. But that may be outdated, so checking in.
>
> I still don't understand why this methodology would cause code to move
> from above to below a comment.
>
> julia
>
You are right Julia. Good methodology, but error in implementation ;)
In reviewing the set of diffs for version 1, I do find that the comment
moved when I picked the comments out for their patch. The bad move is
visible in the comments patch and in the patch where you noticed it in the
diff.
It wasn't intentional. It happened during the partial add. In this
'hunk', as git add calls it, when the changes are too close together to
be hunks, or to split, you get popped into vim to manually edit. That
has to be where I made the mistake.
The partial add is a nice feature. I hope to try it again with these
lessons learned.
alisons
> >
> > Thanks!
> > alison
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20151020232149.GA13649%40Ubuntu-D830.
> > For more options, visit https://groups.google.com/d/optout.
> >
prev parent reply other threads:[~2015-10-21 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 23:21 patchset question Alison Schofield
2015-10-20 23:29 ` [Outreachy kernel] " Greg KH
2015-10-21 5:24 ` Julia Lawall
2015-10-21 17:18 ` Alison Schofield [this message]
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=20151021171811.GA16768@Ubuntu-D830 \
--to=amsfield22@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.com \
/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.