Lines Matching refs:by
12 followed by a Stabilization Period.
32 It is followed by a *Stabilization Period*.
34 The end of a Release Cycle is marked by the release of a new U-Boot version.
86 Sometimes patches miss the Merge Window slightly - say by a few
106 * In Linux, the closing of the merge window is marked by the release of the
147 * Signed-off-by: the *Signed-off-by:* is a line at the end of the commit
148 message by which the signer certifies that they were involved in the development
151 ``Signed-off-by:`` line that contains the developer's name and email address
154 * Please note that in U-Boot, we do not add a ``Signed-off-by`` tag if we
159 however copy ``Signed-off-by`` or other tags.
162 follow the same guidelines as the Linux kernel for `Acked-by
163 ….org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by>`_
164 as well as `Reviewed-by
165 …tml/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-an…
168 * Reviewed-by: The patch has been reviewed and found acceptable according to
171 A *Reviewed-by:* tag is a statement of opinion that the patch is an
174 *Reviewed-by:* tag for a patch.
176 * Acked-by: If a person was not directly involved in the preparation or
178 then they can arrange to have an *Acked-by:* line added to the patch's
181 * Tested-by: A *Tested-by:* tag indicates that the patch has been successfully
182 tested (in some environment) by the person named. Andrew Morton: "I think
188 * Reported-by: If this patch fixes a problem reported by somebody else,
189 consider adding a *Reported-by:* tag to credit the reporter for their
198 explicit action by the person it names. This tag documents that potentially
243 the ``Signed-off-by``, ``Reviewed-by``, etc, tags that have been submitted.