linux-kernel - Re: [PATCH] Rewrite Documentation/SubmittingPatches.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jul 2012 16:41:01 -0700
From:	Junio C Hamano <gitster@...ox.com>
To:	Stefan Beller <stefanbeller@...glemail.com>
Cc:	Rob Landley <rob@...dley.net>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Rewrite Documentation/SubmittingPatches.

Stefan Beller <stefanbeller@...glemail.com> writes:

> +5) "git format-patch HEAD~n"
> +
> +Use "git format-patch HEAD~n" to extract the last n patches from your
> +git repository. They will be be saved in textfiles named
> +
> +    0001-Introduce-new-Feature.patch
> +    0002-Improve-Documentation.patch

Two comments and a half-nit.


 - "--subject-prefix='PATCH v4'" is handy to know (since the
   workflow already assumes reviews and resubmissions in #11).

 - "--cover-letter" is handy to know when sending a multi-patch
   series.

 - "git format-patch -20" or "git format-patch origin" might be more
   familiar looking form than "git format-patch HEAD~20".
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/