Lines Matching refs:email

248 into the sign-off area of your patch (note, NOT an email recipient).  You
288 easiest way to do this is with ``git send-email``, which is strongly
289 recommended.  An interactive tutorial for ``git send-email`` is available at
290 https://git-send-email.io.
292 If you choose not to use ``git send-email``:
308 See :doc:`/process/email-clients` for hints about configuring your e-mail
315 which the patch can be improved, in the form of a reply to your email. You must
327 See :doc:`email-clients` for recommendations on email
353 ``git send-email`` will do this for you automatically.
452 email) listed in the From: line of the email header.
580 alphabetically by subject line - pretty much any email reader will
584 The ``subsystem`` in the email's Subject should identify which
587 The ``summary phrase`` in the email's Subject should concisely
588 describe the patch which that email contains.  The ``summary
593 Bear in mind that the ``summary phrase`` of your email becomes a
633 then the ``From:`` line from the email header will be used to determine
675 (e.g., when using ``git send-email``) to associate the patch with
676 previous relevant discussion, e.g. to link a bug fix to the email with
680 unmanageable forest of references in email clients.  If a link is
682 the cover email text) to link to an earlier version of the patch series.
733 content, right before your email signature.