From: Stephen Haberman <stephen@exigencecorp.com>
To: git@vger.kernel.org
Cc: spearce@spearce.org
Subject: Re: [PATCH v2 RFC] rebase-i-p: squashing and limiting todo
Date: Wed, 8 Oct 2008 02:15:46 -0500 [thread overview]
Message-ID: <20081008021546.c553289f.stephen@exigencecorp.com> (raw)
In-Reply-To: <cover.1223445353.git.stephen@exigencecorp.com>
> This is v2 of my attempt at keeping commits with
> no-parents-being-rewritten off the rebase-i-p todo list.
I forgot to mention, this series almost certainly conflicts with pu's
sh/maint-rebase3. Given that pu is not next, I think I did the right
thing by keeping this series separate, but I can merge them into one
series if that is preferable.
Thanks,
Stephen
prev parent reply other threads:[~2008-10-08 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 6:41 [PATCH v2 RFC] rebase-i-p: squashing and limiting todo Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: test to exclude commits from todo based on its parents Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: use HEAD for updating the ref instead of mapping OLDHEAD Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: delay saving current-commit to REWRITTEN if squashing Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: fix 'no squashing merges' tripping up non-merges Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: only list commits that require rewriting in todo Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: do not include non-first-parent commits touching UPSTREAM Stephen Haberman
2008-10-08 6:41 ` [PATCH v2 RFC] rebase-i-p: if todo was reordered use HEAD as the rewritten parent Stephen Haberman
2008-10-08 7:24 ` [PATCH v2 RFC] rebase-i-p: test to exclude commits from todo based on its parents Junio C Hamano
2008-10-09 1:58 ` Stephen Haberman
2008-10-08 7:15 ` Stephen Haberman [this message]
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=20081008021546.c553289f.stephen@exigencecorp.com \
--to=stephen@exigencecorp.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).