Lines Matching full:series

26 Series-to: fred.blogs@napier.co.nz
28 in one of your commits, the series will be sent there.
39 - Maintain a number of branches, one for each patch series you are
42 series should be sent, cover letter, version, etc. Most of these are
137 there are in your series:
165 commit. Most can only appear once in the whole series.
167 Series-to: email / alias
168 	Email address / alias to send patch series to (you can add this
171 Series-cc: email / alias, ...
172 	Email address / alias to Cc patch series to (you can add this
175 Series-version: n
176 	Sets the version number of this patch series
178 Series-prefix: prefix
186 Series-name: name
187 	Sets the name of the series. You don't need to have a name, and
196 	Sets the cover letter contents for the series. The first line
203 Series-notes:
208 	Sets some notes for the patch series, which you don't want in
236 Series-changes: n
256 Series-process-log: sort, uniq
274 patch series and see how the patches turn out.
281 whole series is sent to the recipients in Series-to: and Series-cc.
318 Here is an example workflow for a series of 4 patches. Let's say you have
349 Now you have an updated patch series. To check it:
365     Series-to: u-boot
366     Series-cc: bfin, marex
367     Series-prefix: RFC
372     cmd_usage() is called all over the place. This series adds a single
379 You want this to be an RFC and Cc the whole series to the bfin alias and
405 update the Series-cc: in the top commit:
407     Series-cc: bfin, marex, Heiko Schocher <hs@denx.de>
409 and remove the Series-prefix: tag since it it isn't an RFC any more. The
410 series is now version two, so the series info in the top commit looks like
413     Series-to: u-boot
414     Series-cc: bfin, marex, Heiko Schocher <hs@denx.de>
415     Series-version: 2
423     Series-changes: 2
431 you have a new series of commits:
442 and it will create and send the version 2 series.
454 3. If you want to keep the commits from each series you sent so that you can