From: | "Michael Sterrett (mr_bones_)" <mr_bones_@g.o> |
---|---|
To: | gentoo-commits@l.g.o |
Subject: | [gentoo-commits] gentoo-x86 commit in net-fs/cifs-utils: cifs-utils-4.8.1.ebuild |
Date: | Fri, 28 Jan 2011 17:06:15 |
Message-Id: | 20110128170605.0C6D720054@flycatcher.gentoo.org |
1 | mr_bones_ 11/01/28 17:06:05 |
2 | |
3 | Modified: cifs-utils-4.8.1.ebuild |
4 | Log: |
5 | whitespace |
6 | |
7 | (Portage version: 2.1.9.25/cvs/Linux i686) |
8 | |
9 | Revision Changes Path |
10 | 1.2 net-fs/cifs-utils/cifs-utils-4.8.1.ebuild |
11 | |
12 | file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild?rev=1.2&view=markup |
13 | plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild?rev=1.2&content-type=text/plain |
14 | diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild?r1=1.1&r2=1.2 |
15 | |
16 | Index: cifs-utils-4.8.1.ebuild |
17 | =================================================================== |
18 | RCS file: /var/cvsroot/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild,v |
19 | retrieving revision 1.1 |
20 | retrieving revision 1.2 |
21 | diff -u -r1.1 -r1.2 |
22 | --- cifs-utils-4.8.1.ebuild 28 Jan 2011 15:15:05 -0000 1.1 |
23 | +++ cifs-utils-4.8.1.ebuild 28 Jan 2011 17:06:04 -0000 1.2 |
24 | @@ -1,6 +1,6 @@ |
25 | # Copyright 1999-2011 Gentoo Foundation |
26 | # Distributed under the terms of the GNU General Public License v2 |
27 | -# $Header: /var/cvsroot/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild,v 1.1 2011/01/28 15:15:05 vostorga Exp $ |
28 | +# $Header: /var/cvsroot/gentoo-x86/net-fs/cifs-utils/cifs-utils-4.8.1.ebuild,v 1.2 2011/01/28 17:06:04 mr_bones_ Exp $ |
29 | |
30 | EAPI=2 |
31 | |
32 | @@ -65,7 +65,7 @@ |
33 | } |
34 | |
35 | pkg_postinst() { |
36 | - # Inform about set-user-ID bit of mount.cifs |
37 | + # Inform about set-user-ID bit of mount.cifs |
38 | if use setuid ; then |
39 | ewarn "Setting SETUID bit for mount.cifs." |
40 | ewarn "However, there may be severe security implications. Also see:" |