Lines Matching full:your

10 - Creates patch directly from your branch
20 It is configured almost entirely by tags it finds in your commits.
28 in one of your commits, the series will be sent there.
30 In Linux and U-Boot this will also call get_maintainer.pl on each of your
47 - Check out a branch, and run this script to create and send out your
56 file 'doc/git-mailrc' in your U-Boot directory to supply the email aliases
68 To add your own, create a file ~/.patman like this:
85 used. Failing that you can put it into your path or ~/bin/checkpatch.pl
88 by patman but are known to bounce you can add a [bounces] section to your
101 you can add a [settings] section to your .patman file.  This can be used
118 [project_alias].  If you want to use tags for your linux work, you could
137 there are in your series:
141 This will create patch files in your current directory and tell you who
147 is useful if your top commit is for setting up testing.
183 	well. If your format.subjectprefix is set to InternalProject, then
222 	A sign-off is added automatically to your patches (this is
223 	probably a bug). If you put this tag in your patches, it will
230 	These indicate that someone has tested/reviewed/acked your patch.
246 	By adding your change lists into your commits it is easier to
273 Exercise for the reader: Try adding some tags to one of your current
315 The basic workflow is to create your commits, add some tags to the top
320 your tree where 'us' means your upstreaming activity (newest to oldest as
329 The first patch is some test things that enable your code to be compiled,
358 Use your editor to add some tags, so that the whole commit message is:
388 The patches will be created, shown in your editor, and then sent along with
390 people on the list don't see your secret info.
395 so you can drop your wip commit. So you resync with upstream:
446 1. When you change back to the us-cmd branch days or weeks later all your
463 this in your editor, but be careful!