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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 12 Feb 2009 18:16:28 -0800
From:	Junio C Hamano <junio@...ox.com>
To:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:	Ingo Oeser <ioe-lkml@...eria.de>,
	Peter Zijlstra <peterz@...radead.org>,
	L-K <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: git-send-email

lsorense@...lub.uwaterloo.ca (Lennart Sorensen) writes:

> On Thu, Feb 12, 2009 at 06:25:34PM +0100, Ingo Oeser wrote:
>> No, they are great, if you like to skip over a topic, you are not
>> interested in at all!
>> 
>> If you don't like it, just switch off thread in your mailer and
>> don't force this on everybody else!
>
> Actually if (as apparently many people seem to manage to do) you have a
> single starting email, with all the patches as replies to that first
> email, it looks a lot better, and is much easier to follow.
>
> Seperate threads would be bad.
>
> foobar patch 0 (usually a summary/overview)
> +-foobar patch 1
> +-foobar patch 2
> +-foobar patch 3
> +-foobar patch 4
> +-foobar patch 5
>
> is much nicer than
>
> foobar patch 0
> +-foobar patch 1
>   +-foobar patch 2
>     +-foobar patch 3
>       +-foobar patch 4
>         +-foobar patch 5
>
> which seems to be what git does itself.

I personally prefer the former, but as you hopefully all found out by now,
the choice between these two is just the matter of personal taste, and
there is no clear majority.

The default will not going to change.

--
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/

Powered by blists - more mailing lists