Lines Matching refs:series

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.
168 	Email address / alias to send patch series to (you can add this
172 	Email address / alias to Cc patch series to (you can add this
176 	Sets the version number of this patch series
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
208 	Sets some notes for the patch series, which you don't want in
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:
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
410 series is now version two, so the series info in the top commit looks like
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