From: "Shawn O. Pearce" <spearce@spearce.org>
To: Stephen Haberman <stephen@exigencecorp.com>
Cc: Avi Kivity <avi@redhat.com>, git@vger.kernel.org
Subject: Re: [PATCH RFC] rebase--interactive: if preserving merges, use first-parent to limit what is shown.
Date: Tue, 7 Oct 2008 07:38:02 -0700 [thread overview]
Message-ID: <20081007143802.GI8203@spearce.org> (raw)
In-Reply-To: <20081007013654.274e5cf6.stephen@exigencecorp.com>
Stephen Haberman <stephen@exigencecorp.com> wrote:
> However, lest I burn my "PATCH v2" opportunity, I'm holding off on
> posting the updated patch. It works and passes tests but I'm sure I'll
> tinker with it some more over the next few days. It will also likely
> conflict with my pu sh/maint-rebase3 patch, so I don't know whether to
> base it on top of that one or not (guessing not).
When a patch series is in `pu` it can be rebased/replaced/amended
at any time. That's why I parked it there. The pu branch rewinds
and is rebuilt on a daily basis. Any commits not yet merged into
maint, master or next are automatically rebased onto the latest
maint or master branch and get merged into that day's pu.
So don't hold back on posting patches. Folks expect to see
patches on this list; talking is less productive than posting code.
Showing code that purports to solve a problem, or that at least
displays a problem concretely is worthy of discussion.
And don't worry about replacing what is currently in pu. Its easily
done by the maintainer. However don't expect daily updates to a
topic in pu. Junio (and I) just don't have the bandwidth to keep
replacing patches every day.
--
Shawn.
next prev parent reply other threads:[~2008-10-07 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 15:30 git rebase -i -p broken? Avi Kivity
2008-10-06 15:21 ` [PATCH RFC] rebase--interactive: if preserving merges, use first-parent to limit what is shown Stephen Haberman
2008-10-07 2:20 ` Stephen Haberman
2008-10-07 6:36 ` Stephen Haberman
2008-10-07 14:38 ` Shawn O. Pearce [this message]
2008-10-07 9:57 ` Avi Kivity
2008-10-07 12:07 ` Stephan Beyer
2008-10-07 12:22 ` Avi Kivity
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=20081007143802.GI8203@spearce.org \
--to=spearce@spearce.org \
--cc=avi@redhat.com \
--cc=git@vger.kernel.org \
--cc=stephen@exigencecorp.com \
/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).