Git development
 help / color / mirror / Atom feed
From: Greg Price <price@ksplice.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v2 0/1] Fix rebase -p --onto
Date: Wed, 22 Jul 2009 13:36:36 -0400	[thread overview]
Message-ID: <20090722173635.GN7878@vinegar-pot.mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0907221905360.7343@intel-tinevez-2-302>

On Wed, Jul 22, 2009 at 07:07:17PM +0200, Johannes Schindelin wrote:
> On Wed, 22 Jul 2009, Greg Price wrote:
> > [...] when the great day comes that rebase -i -p can reorder commits 
> 
> If you want to help, I would be so thankful.  In that case, it might make 
> more sense to hold off this patch and integrate it into the rebase-i-p 
> patch series, rather than requiring a rebase of rebase-i-p on top of your 
> patches, which will postpone said day only further.

Where is your patch series and what are the big things that need doing
before it can be merged?  I can't promise a great deal of time up
front, but I would be glad to look at it and may be able to pitch in.

Because this patch is about --onto together with -p and doesn't really
involve -i, I think it still makes sense to merge.  It's only one line
plus tests, so I don't think it will create that much of a rebase burden.

Cheers,
Greg

  reply	other threads:[~2009-07-22 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 16:37 [PATCH v2 0/1] Fix rebase -p --onto Greg Price
2009-07-22 16:38 ` [PATCH v2 1/1] " Greg Price
2009-07-22 17:07 ` [PATCH v2 0/1] " Johannes Schindelin
2009-07-22 17:36   ` Greg Price [this message]
2009-07-22 18:05     ` Johannes Schindelin

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=20090722173635.GN7878@vinegar-pot.mit.edu \
    --to=price@ksplice.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    /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