os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Specify that committers should use a umask of 2 on freefall, so that

Browse source 
files/directories added to the repository get the correct group-writable
permission.
This commit is contained in:
Ben Smithurst 2000-08-23 20:36:53 +00:00
parent caf2efb445
commit fda7bf8bf8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7877
2 changed files with 30 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.34 2000/08/15 01:39:50 kuriyama Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.35 2000/08/16 17:41:40 dannyboy Exp $</pubdate>
<copyright>
<year>1999</year>
@ -136,6 +136,17 @@
arguments and it will prompt you for everything it needs to
know.</para>
<para>Note that when you use CVS on <hostid>freefall</hostid>, you
should set your <literal>umask</literal> to <literal>2</literal>,
as well as setting the <literal>CVSUMASK</literal> environmenet
variable to <literal>2</literal>. This ensures that any new
files created by <command>cvs add</command> will have the correct
permissions. If you add a file or directory and discover that the
file in the repository has incorrect permissions (specifically,
all files in the repository should be group writable by group
<literal>ncvs</literal>), contact one of the repository meisters
as described below.</para>
<para>If you are familiar with remote CVS and consider yourself
pretty studly with CVS in general, you can also do CVS
operations directly from your own machine and local working
@ -520,11 +531,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> (or in FreeBSD's case,
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> line intact).</para>
</listitem>
<listitem>

19
en_US.ISO_8859-1/articles/committers-guide/article.sgml
View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.34 2000/08/15 01:39:50 kuriyama Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.35 2000/08/16 17:41:40 dannyboy Exp $</pubdate>
<copyright>
<year>1999</year>
@ -136,6 +136,17 @@
arguments and it will prompt you for everything it needs to
know.</para>
<para>Note that when you use CVS on <hostid>freefall</hostid>, you
should set your <literal>umask</literal> to <literal>2</literal>,
as well as setting the <literal>CVSUMASK</literal> environmenet
variable to <literal>2</literal>. This ensures that any new
files created by <command>cvs add</command> will have the correct
permissions. If you add a file or directory and discover that the
file in the repository has incorrect permissions (specifically,
all files in the repository should be group writable by group
<literal>ncvs</literal>), contact one of the repository meisters
as described below.</para>
<para>If you are familiar with remote CVS and consider yourself
pretty studly with CVS in general, you can also do CVS
operations directly from your own machine and local working
@ -520,11 +531,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> (or in FreeBSD's case,
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.35 2000-08-16 17:41:40 dannyboy Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.36 2000-08-23 20:36:53 ben Exp $</literal> line intact).</para>
</listitem>
<listitem>