ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Christoph Lameter <cl@linux.com>,
	"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 08:18:17 -0700	[thread overview]
Message-ID: <20160729151817.GD12137@x> (raw)
In-Reply-To: <CAKMK7uF5ZVi_5m1_Fp6GR6YoC-4eiKuLmx4GtOAxiJOXWZF5RQ@mail.gmail.com>

On Fri, Jul 29, 2016 at 05:00:06PM +0200, Daniel Vetter wrote:
> On Fri, Jul 29, 2016 at 4:21 PM, Christoph Lameter <cl@linux.com> wrote:
> > 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.
> 
> Shameless plug of our own tooling for maintainer a quilt pile and
> tracking it in git:
> 
> https://cgit.freedesktop.org/drm-intel/tree/qf?h=maintainer-tools
> 
> It even tracks the baseline sha1 and pulls/pushes it in hidden remote
> refs/. Which all together allows you to git bisect on the quilt
> branch, which is a really powerful thing for a long-lived rebasing
> patch pile. quilt+git was the only thing that allowed me to glue
> something git bisect capable together.

By "bisect on the quilt branch", do you mean bisecting between versions
of the overall patch series?

That does seem quite helpful, if you need to figure out at what point a
change occurred in the patch series to break something.  I've filed
https://github.com/git-series/git-series/issues/3 about supporting that.

> And the other reason is the same you have: Editing raw patches is
> really powerful for doing rebases over mechanical changes. Function
> renames become a trivial quilt pop -a ; sed; while quilt push ; do
> make ; done.

Interesting!  I'll have to give that some thought, to figure out if
I can support workflows like that.

What other kinds of changes do you tend to make by editing patches
directly?

I'm tempted to add a "git series filter" that applies filter-branch to
the commits in the series, or something similar to that.  I'll also have
to think about the use case of testing each commit in the series, to see
if that needs support from git-series or just from underlying git tools.

- Josh Triplett

  reply	other threads:[~2016-07-29 15:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  7:50 Josh Triplett
2016-07-29 12:20 ` David Howells
2016-07-29 13:11   ` 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: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 [this message]
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
2016-07-29 21:59           ` James Hogan
2016-07-30  2:55           ` Steven Rostedt
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 14:34     ` Josh Triplett
2016-07-29 14:37     ` David Howells
2016-07-29 14:56       ` Josh Triplett
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=20160729151817.GD12137@x \
    --to=josh@joshtriplett.org \
    --cc=cl@linux.com \
    --cc=daniel.vetter@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox