I was thinking of something that git itself (or one of its support tools) might understand, but thanks.
On Thu, Dec 18, 2014 at 5:40 AM, Taras Kondratiuk < [email protected]> wrote: > > On 12/18/2014 01:31 PM, Bill Fischofer wrote: > >> Ok, I hadn't noticed that. As an aside, is there a standard for >> specifying pre-reqs / co-reqs for patches? With so many patches "in >> flight" it can be confusing to know what all the dependency chains are. >> > > Usually dependency or other important notes that should not be a part > of git history are specified: > > 1. In a cover letter if a series has it. > 2. Under '---' in case of a single patch. > 3. Directly in a commit message if it is RFC patch. >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
