Lines Matching refs:series
26 in one of your commits, the series will be sent there.
37 - Maintain a number of branches, one for each patch series you are
40 series should be sent, cover letter, version, etc. Most of these are
136 there are in your series:
164 commit. Most can only appear once in the whole series.
167 Email address / alias to send patch series to (you can add this
171 Email address / alias to Cc patch series to (you can add this
175 Sets the version number of this patch series
186 Sets the name of the series. You don't need to have a name, and
195 Sets the cover letter contents for the series. The first line
207 Sets some notes for the patch series, which you don't want in
273 patch series and see how the patches turn out.
280 whole series is sent to the recipients in Series-to: and Series-cc.
317 Here is an example workflow for a series of 4 patches. Let's say you have
348 Now you have an updated patch series. To check it:
371 cmd_usage() is called all over the place. This series adds a single
378 You want this to be an RFC and Cc the whole series to the bfin alias and
409 series is now version two, so the series info in the top commit looks like
430 you have a new series of commits:
441 and it will create and send the version 2 series.
453 3. If you want to keep the commits from each series you sent so that you can