git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Andy Parkins <andyparkins@gmail.com>,
	git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>
Subject: Re: Some ideas for StGIT
Date: Sat, 04 Aug 2007 20:08:23 -0400	[thread overview]
Message-ID: <1186272503.1948.21.camel@dv> (raw)
In-Reply-To: <20070804055110.GP20052@spearce.org>

On Sat, 2007-08-04 at 01:51 -0400, Shawn O. Pearce wrote:

> I agree with Andy.  Aside from the performance issues that I
> am currently having with a 55 patch series, "rebase -i" (and its
> predecessor script from Dscho) have been a major part of my toolkit,
> to the point that I really don't need something like StGIT on
> my system.
> 
> (Regarding the performance, cherry-picking 55 patches is
> slow, especially when many of them would apply trivially with
> git-diff|git-apply --index.  Be nice to improve that in 1.5.4.)

I understand that "git-rebase -i" is good for keeping local changes
up-to-date, but the real issue is managing the local patches so that
they can be enhanced to the point that they are ready for submission.

That includes such things as moving chunks between patches, editing
descriptions, joining patches together, sorting patches into groups by
their urgency and so on.  Keeping the patches up-to-date is just one
aspect.

Anyway, I'm going to give "git-rebase -i" a try.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2007-08-05  0:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 17:50 Some ideas for StGIT Pavel Roskin
2007-08-03 18:14 ` Andy Parkins
2007-08-04  5:41   ` Pavel Roskin
2007-08-04  5:51     ` Shawn O. Pearce
2007-08-05  0:08       ` Pavel Roskin [this message]
2007-08-05  0:17       ` Jakub Narebski
2007-08-05  2:31         ` Shawn O. Pearce
2007-08-05  3:32           ` Junio C Hamano
2007-08-05 13:39           ` Josef Sipek
2007-08-05 13:56             ` Johannes Schindelin
2007-08-05 14:06               ` Josef Sipek
2007-08-05 14:15                 ` Johannes Schindelin
2007-08-05 14:57                   ` Josef Sipek
2007-08-04  8:08     ` Yann Dirson
2007-08-06 10:01       ` Catalin Marinas
2007-08-04 14:14     ` Chris Shoemaker
2007-08-04 15:22       ` Johannes Schindelin
2007-08-03 23:23 ` Yann Dirson
2007-08-06  9:49   ` Catalin Marinas
2007-08-06 13:26     ` Pavel Roskin
2007-08-06 15:19       ` Josef Sipek
2007-08-04  6:38 ` Theodore Tso
2007-08-04  8:16   ` Yann Dirson
2007-08-04 21:35   ` Josef Sipek
2007-08-05  0:12     ` Pavel Roskin
2007-08-06  9:36 ` Catalin Marinas
2007-08-06  9:56   ` Karl Hasselström
2007-08-06 12:42     ` Pavel Roskin
2007-08-06 13:52       ` Karl Hasselström
2007-08-23 14:09         ` Catalin Marinas
2007-08-23 14:34           ` Karl Hasselström
2007-08-06 17:17   ` Pavel Roskin

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=1186272503.1948.21.camel@dv \
    --to=proski@gnu.org \
    --cc=andyparkins@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).