From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sven@narfation.org>
From: Sven Eckelmann <sven@narfation.org>
Date: Sat, 27 Feb 2016 12:31:05 +0100
Message-ID: <2909292.ZAgPzXvjgZ@sven-edge>
In-Reply-To: <OF34C428B5.B1B9DB61-ONC1257F66.00389705-C1257F66.003D570A@phoenixcontact.com>
References: <20160226141638.169e15ae@ubuntu> <2279019.udanyR4lfT@bentobox>
 <OF34C428B5.B1B9DB61-ONC1257F66.00389705-C1257F66.003D570A@phoenixcontact.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2824777.qPfsymot6Y";
 micalg="pgp-sha512"; protocol="application/pgp-signature"
Subject: Re: [B.A.T.M.A.N.] Antwort: Re: [Patchv2 0/7] batman-adv:
	Optimizations for setups running dat and bla
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n.lists.open-mesh.org>
List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe>
List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/>
List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org>
List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help>
List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe>
To: Andreas Pape <APape@phoenixcontact.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org

--nextPart2824777.qPfsymot6Y
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Saturday 27 February 2016 12:10:00 Andreas Pape wrote:
> Is there a way to generate the cover letter also with git send-email? As I
> did
> not know how to generate it, I used claws as a separate e-mail client.

I've already explained this earlier [1]:

    git send-email --compose 0001-.... 0002-... ....

The --compose option should force git-send-email to open an $EDITOR which then
can be used to write a separate message. But you can also just create manually
a 0000-* file with the same valid mail headers (like the ones in a patch
generated by git-format-patch) and add it as first file to `git send-email`.

> I used checkpatch.pl of linux 4.5 rc5 and checked each patch seperately
> without open
> issues. These things with bracket alignment etc. start driving me crazy.
> Looks as if I don't
> use a proper editor. Can you recommend one to use before sending patches?

Every editor which can be configured to represent one tab as 8 spaces. I
personally use kate or vim.

You should use checkpatch.pl with --strict. And you can also try to check the
original source file with bracket_align.py [2]. Btw. I personally use
checkpatch.pl from linux-next [3] because it usually has some new checks
which are not yet in Linus' tree.

Kind regards,
	Sven

[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-February/014491.html
[2] https://git.open-mesh.org/build_test.git/blob_plain/HEAD:/testhelpers/bracket_align.py
[3] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/
--nextPart2824777.qPfsymot6Y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCgAGBQJW0Yj5AAoJEF2HCgfBJntGb8AP/3LplZIt27cDC42fEIi9c9zq
sHRnXrZLH9fF/Y1bVg26tEL36C01UDX9qIgI4g8zUhsRONuLbtkXwuNo2i+YQTNH
WRgWAnBUmIvHws7KUIaRbPUVFSuVG7xBzdkQA7G7PftvxTNgnZtMUMuUAjF0I/9R
XlW31VNDk74UkNSocwLQtcIVqdGUdpf50tPMHNbGkXETFmWCSRJYAsaTFOF7FG7h
4PktY9EmV/Er7AP1YLb72GTaJPUXJ4URVPz8MuokGRotfsQviPdODOAJkbgrdLxO
Ccm9oUDJC8cLhstOt8I3tReu6IE3jZ3c0EtVm9FHDZPwsjdKGgcQiJTHboMlnOHw
LoZELm3JyK9388nvWeX/rGPnHWhjw75Tw0B6dIeO79xqDyzG6kdg0Ywo/hT42b5G
+nDeICTIrrDPlpl0ZAE7ctYEhXM/QC6zMDZq3KNBvXLvgIMmaascigb0t+F7bkSe
q54xz2DksvfA6zEuEHf/CffPtwSDY8oE8+CjPJdr6G3/HFtB7WPQ1pGAatgjIL2i
RKuJiIoh/3Al7h3MzH0HHc7c9ydUINT555iF3W1Z5T+EEpsp+KxORNQabqV1UcZh
qla2k5dMy2rCrXmCkRf+OMUmMU1Z8TgP+XBsJlUwu3AJXzFxUIObWVkNHVDgidYc
RdRu4LHZc1pdxdr2b+er
=uk+U
-----END PGP SIGNATURE-----

--nextPart2824777.qPfsymot6Y--