All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Bird, Timothy" <Tim.Bird@am.sony.com>,
	Christoph Lameter <cl@linux.com>,
	 David Howells <dhowells@redhat.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [ANNOUNCE] git-series: track changes to a patch series over time
Date: Fri, 29 Jul 2016 10:57:26 -0700	[thread overview]
Message-ID: <1469815046.2330.13.camel@HansenPartnership.com> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF053BB894@USCULXMSG02.am.sony.com>

On Fri, 2016-07-29 at 17:52 +0000, Bird, Timothy wrote:
> 
> > -----Original Message-----
> > From: ksummit-discuss-bounces@lists.linuxfoundation.org [mailto:ksu
> > mmit-
> > discuss-bounces@lists.linuxfoundation.org] On Behalf Of Christoph
> > Lameter
> > Sent: Friday, July 29, 2016 7:21 AM
> > To: David Howells <dhowells@redhat.com>
> > Cc: ksummit-discuss@lists.linuxfoundation.org
> > Subject: Re: [Ksummit-discuss] [ANNOUNCE] git-series: track changes
> > to a patch
> > series over time
> > 
> > On Fri, 29 Jul 2016, David Howells wrote:
> > 
> > > Josh Triplett <josh@joshtriplett.org> wrote:
> > > 
> > > > Note that git-series doesn't provide a quilt-style push/pop
> > > > workflow,
> > > > with applied and unapplied patches; it just looks at HEAD.
> > > 
> > > Ah...  In that case it's probably not a sufficient substitute for
> > > how I use
> > > stgit.
> > 
> > Did not know that there was stgit. Still stuck on quilt since
> > I like editing the files directly (its often easier to edit the
> > diffs if
> > you want to rename things etc).
> > 
> > Interesting projects.
> 
> Indeed.  For many years I used a quilt-based workflow.  Recently
> I've been trying to convert to a pure git-based workflow, but for
> some reason git rebase -I always seems to give me problems.  It
> always takes me much longer to just move some hunk from one
> commit to another than it did in quilt using the patches and vi.

I do this too, but I also work with the diff when moving hunks.  What I
do is:

git checkout <removal commit>
git show <removal commit> > tmp.diff
vi tmp.diff so it only has the hunks I want to remove
patch -p1 -R < ~/tmp.diff
git commit --amend -a
git checkout <add commit>
patch -p1 < ~/tmp.diff
git commit --amend -a

It's a bit cumbersome, but you can script it.  If there are better ways
to do it, I'm interested.

James

  reply	other threads:[~2016-07-29 17:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  7:50 [Ksummit-discuss] [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett
2016-07-29 12:20 ` David Howells
2016-07-29 13:11   ` Josh Triplett
2016-07-29 14:06     ` David Howells
2016-07-29 14:21       ` Christoph Lameter
2016-07-29 14:37         ` Josh Triplett
2016-07-29 15:00         ` Daniel Vetter
2016-07-29 15:18           ` Josh Triplett
2016-07-29 15:40             ` Daniel Vetter
2016-07-29 16:21               ` Josh Triplett
2016-07-29 16:31                 ` Luis R. Rodriguez
2016-07-29 17:52         ` Bird, Timothy
2016-07-29 17:57           ` James Bottomley [this message]
2016-07-29 20:13             ` David Howells
2016-07-30  5:02               ` Josh Triplett
2016-07-30  8:43                 ` Arnd Bergmann
2016-08-04 12:44                 ` Jani Nikula
2016-07-29 21:59             ` James Hogan
2016-07-30  2:55             ` Steven Rostedt
2016-07-29 14:34       ` Josh Triplett
2016-07-29 14:37         ` David Howells
2016-07-29 14:56           ` Josh Triplett
2016-08-04 22:46     ` Catalin Marinas
2016-08-04 23:07       ` Michael S. Tsirkin
2016-08-08 17:27         ` Catalin Marinas
2016-08-15 23:44           ` Michael S. Tsirkin
2016-08-04 23:46       ` Josh Triplett
2016-08-08 17:37         ` Catalin Marinas
2016-07-29 14:55 ` James Bottomley
2016-07-29 15:05   ` Josh Triplett
2016-08-09  0:10     ` Paul E. McKenney
2016-07-29 15:26 ` James Hogan
2016-08-04 23:52 ` Michael S. Tsirkin
2016-08-05 20:26   ` Josh Triplett
2016-08-15 13:20     ` James Hogan
2016-08-15 16:14       ` Josh Triplett
2016-08-15 23:42     ` Michael S. Tsirkin
2016-08-15 12:53 ` James Hogan
2016-08-15 16:34   ` Josh Triplett
2016-08-15 18:46     ` James Hogan
2016-08-15 21:35       ` Josh Triplett
2016-08-15 22:06         ` James Hogan
2016-08-15 23:59           ` Josh Triplett
2016-08-16  2:38             ` Michael S. Tsirkin

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=1469815046.2330.13.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Tim.Bird@am.sony.com \
    --cc=cl@linux.com \
    --cc=dhowells@redhat.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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.