Re: [PATCH RFC] rebase--interactive: if preserving merges, use first-parent to limit what is shown.

From: Shawn O. Pearce <spearce@spearce.org>
Date: Oct 7, 2008, 14:38 UTC
Message-ID: <20081007143802.GI8203@spearce.org>
In-Reply-To: <20081007013654.274e5cf6.stephen@exigencecorp.com>

Stephen Haberman <stephen@exigencecorp.com> wrote:

Show 5 quoted lines

> 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.