From: Josh Triplett <josh@joshtriplett.org>
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
Date: Fri, 29 Jul 2016 07:56:35 -0700 [thread overview]
Message-ID: <20160729145635.GA12137@x> (raw)
In-Reply-To: <2984.1469803044@warthog.procyon.org.uk>
On Fri, Jul 29, 2016 at 03:37:24PM +0100, David Howells wrote:
> Josh Triplett <josh@joshtriplett.org> wrote:
> > You could use the two together, though, if you'd like to track the
> > history you've changed with stgit. You'd just need to make sure you'd
> > applied all the patches before doing a git series commit.
>
> Would it be possible to make stgit run on top of git series?
Possibly; it would depend on what you mean by "run on top of". I'm open
to suggestion, though.
> Or extend git series to also do the push/pop thing?
I'll have to give that workflow some thought. The concept of a "patch
that isn't applied" seems somewhat orthogonal to git-series.
next prev parent reply other threads:[~2016-07-29 14:56 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-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
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 [this message]
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=20160729145635.GA12137@x \
--to=josh@joshtriplett.org \
--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.