Re: [PATCH] grep: provide pathspecs/patterns via file or stdin

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 23, 2019, 00:28 UTC
Message-ID: <xmqqsgmf3071.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20191122220241.GA56020@google.com>

Emily Shaffer <emilyshaffer@google.com> writes:

> In this situation - where it is not a related fixup for a branch in
> next, but the topic does rely on that branch - should I send a series
> which is based on 'next'? How do I make the dependency clear to you via
> emailed patch?

If you need to use a particular new feature from a topic (or two), not depending on 'next' but either building on

 (1) directly that topic, or

 (2) a local merge you create across the 'master' branch and the
     topic(s) you want to depend on

would be good. Whichever way you go, leaving a note either on the cover letter or after the three-dash line to say what you did would always be helpful to the reviewers.

In this particular case, I think (1) would work better for you, as the topic you want to use builds directly on the latest release so you won't be missing anything that is not yet on that topic but already in 'master' at this point.

Thanks.