0 | |
From: intrigeri <intrigeri@boum.org>
|
1 | |
Date: Fri, 5 Oct 2012 19:56:13 +0200
|
2 | |
Subject: Bypass root's mutt configuration file.
|
3 | |
|
4 | |
In case the root user has configured mutt, in their $HOME, for their own
|
5 | |
interactive use, we don't want these tweaks to impact the non-interactive use
|
6 | |
metche makes of mutt in any way.
|
7 | |
|
8 | |
In case the administrator wants to configure mutt for interactive *and*
|
9 | |
non-interactive use, they'd better edit its system-wide configuration file.
|
10 | |
|
11 | |
As mentioned by Andreas Beckmann, a mutt configuration file for the root user
|
12 | |
may trigger more occurrences of Debian bug #657071 than needed :)
|
|
0 |
Description: Bypass root's mutt configuration file
|
|
1 |
Subject:Bypass root's mutt configuration file.In case the root user has configured mutt, in their $HOME, for their own
|
|
2 |
interactive use, we don't want these tweaks to impact the non-interactive use
|
|
3 |
metche makes of mutt in any way.
|
|
4 |
.
|
|
5 |
In case the administrator wants to configure mutt for interactive *and*
|
|
6 |
non-interactive use, they'd better edit its system-wide configuration file.
|
|
7 |
.
|
|
8 |
As mentioned by Andreas Beckmann, a mutt configuration file for the root user
|
|
9 |
may trigger more occurrences of Debian bug #657071 than needed :)
|
|
10 |
From:intrigeri <intrigeri@boum.org>
|
|
11 |
Bug-Debian: https://bugs.debian.org/657071
|
|
12 |
Origin: upstream, commit:1e61154f49422f2d718f34114991f92861370718
|
13 | 13 |
---
|
14 | 14 |
metche | 2 +-
|
15 | 15 |
1 file changed, 1 insertion(+), 1 deletion(-)
|