linux-kernel - Re: [PATCH 0/6] Lazy workqueues

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:	Mon, 24 Aug 2009 02:03:23 -0700
From:	Junio C Hamano <junio@...ox.com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, jeff@...zik.org,
	benh@...nel.crashing.org, htejun@...il.com, bzolnier@...il.com,
	alan@...rguk.ukuu.org.uk
Subject: Re: [PATCH 0/6] Lazy workqueues

Jens Axboe <jens.axboe@...cle.com> writes:

> OK that's at least something, looking forward to being able to prune
> that argument from my scripts.

Ahahh.

An option everybody will want to pass but is prone to be forgotten and
hard to type from the command line is one thing, but if you are scripting
in order to reuse the script over and over, that is a separate story.  Is
losing an option from your script really the goal of this fuss?

In any case, you not need to wait for a new version nor a patch at all for
that goal.  You can simply add

[sendemail]
	chainreplyto = no

to your .git/config (or $HOME/.gitconfig).  Both your script and your
command line invocation will default not to create deep threads with the
setting.

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