[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Cvs-cvs] ccvs/doc/i18n/pt_BR cvs.texinfo
From: |
Fred Ulisses Maranhão |
Subject: |
[Cvs-cvs] ccvs/doc/i18n/pt_BR cvs.texinfo |
Date: |
Fri, 03 Feb 2006 23:25:58 +0000 |
CVSROOT: /sources/cvs
Module name: ccvs
Branch:
Changes by: Fred Ulisses Maranhão <address@hidden> 06/02/03 23:25:58
Modified files:
doc/i18n/pt_BR : cvs.texinfo
Log message:
translated "A.6 admin - Administration"
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/cvs/ccvs/doc/i18n/pt_BR/cvs.texinfo.diff?tr1=1.40&tr2=1.41&r1=text&r2=text
Patches:
Index: ccvs/doc/i18n/pt_BR/cvs.texinfo
diff -u ccvs/doc/i18n/pt_BR/cvs.texinfo:1.40
ccvs/doc/i18n/pt_BR/cvs.texinfo:1.41
--- ccvs/doc/i18n/pt_BR/cvs.texinfo:1.40 Sun Jan 15 06:39:34 2006
+++ ccvs/doc/i18n/pt_BR/cvs.texinfo Fri Feb 3 23:25:57 2006
@@ -9317,8 +9317,8 @@
solução em alguns sistemas de controle de versão,
incluindo @sc{rcs} e @sc{sccs}. Atualmente, a forma
normal de se ter ???checkouts??? reservados com o @sc{cvs}
-é com o comando @code{cvs admin -l} (@pxref{admin
-options}). Isto não é tão integrado com o @sc{cvs}
+é com o comando @code{cvs admin -l} (@pxref{Opções do
+admin}). Isto não é tão integrado com o @sc{cvs}
quanto a habilidade de ???watch???, descrita abaixo,
mas vemos que a maioria das pessoas que necessitam de
???checkouts??? reservados acham isto adequado.
@@ -11340,7 +11340,7 @@
@c <en>The state assigned to the revision. States can be
@c <en>assigned with @code{cvs admin -s}---see @ref{admin options}.
O estado atribuído à revisão. Estados podem ser
-atribuídos com @code{cvs admin -s}---veja em @ref{admin options}.
+atribuídos com @code{cvs admin -s}---veja em @ref{Opções do admin}.
@c <en>@cindex Local keyword
@cindex Palavra-chave Local
@@ -12240,7 +12240,7 @@
@c <en>You must specify the @samp{-bFSF_DIST} without any space
@c <en>after the @samp{-b}. @xref{admin options}.
Você deve especificar o @samp{-bFSF_DIST} sem botar
-espaços depois do @samp{-b}. @xref{admin options}.
+espaços depois do @samp{-b}. @xref{Opções do admin}.
@c <en>@node Binary files in imports
@node Arquivos binários em importações
@@ -13801,7 +13801,7 @@
Você pode usar esta opção repetidamente. O argumento
pode ser uma expressão regular de nome de arquivo do
mesmo tipo dos que se especifica no arquivo
address@hidden Disponívjel nos seguintes
address@hidden Disponível nos seguintes
comandos: @code{import} e @code{update}.
@end table
@@ -13820,50 +13820,81 @@
Synonym: rcs
@end itemize
-This is the @sc{cvs} interface to assorted
-administrative facilities. Some of them have
-questionable usefulness for @sc{cvs} but exist for
-historical purposes. Some of the questionable options
-are likely to disappear in the future. This command
address@hidden work recursively, so extreme care should be
-used.
+Esta é a interface do @sc{cvs} para agrupar
+???facilities??? administrativas. Algumas delas tem
+utilidade questionável no @sc{cvs} mas existem por
+questões históricas. Algumas destas opções questionáves
+devem desaparecer no futuro. Este comando @emph{NÃO}
+trabalha recursivamente, portanto deve-se ter muito
+cuidado quando usá-lo.
address@hidden <en>@cindex cvsadmin
@cindex cvsadmin
address@hidden UserAdminOptions, in CVSROOT/config
-On unix, if there is a group named @code{cvsadmin},
-only members of that group can run @code{cvs admin}
-commands, except for those specified using the
address@hidden configuration option in the
address@hidden/config} file. Options specified using
address@hidden can be run by any user. See
address@hidden for more on @code{UserAdminOptions}.
-
-The @code{cvsadmin} group should exist on the server,
-or any system running the non-client/server @sc{cvs}.
-To disallow @code{cvs admin} for all users, create a
-group with no users in it. On NT, the @code{cvsadmin}
-feature does not exist and all users
-can run @code{cvs admin}.
address@hidden <en>@cindex UserAdminOptions, in CVSROOT/config
address@hidden UserAdminOptions, em CVSROOT/config
address@hidden <en>On unix, if there is a group named @code{cvsadmin},
address@hidden <en>only members of that group can run @code{cvs admin}
address@hidden <en>commands, except for those specified using the
address@hidden <en>@code{UserAdminOptions} configuration option in the
address@hidden <en>@file{CVSROOT/config} file. Options specified using
address@hidden <en>@code{UserAdminOptions} can be run by any user. See
address@hidden <en>@ref{config} for more on @code{UserAdminOptions}.
+No unix, se existe um grupo chamado @code{cvsadmin},
+apenas membros deste grupo podem rodar os comandos do
address@hidden admin}, exceto aqueles especificados na opção
address@hidden do arquivo
address@hidden/config}. Opções especificadas usando o
address@hidden podem ser executadas por
+qualquer usuário. Veja em @ref{config} para mais
+informações sobre o @code{UserAdminOptions}.
+
address@hidden <en>The @code{cvsadmin} group should exist on the server,
address@hidden <en>or any system running the non-client/server @sc{cvs}.
address@hidden <en>To disallow @code{cvs admin} for all users, create a
address@hidden <en>group with no users in it. On NT, the @code{cvsadmin}
address@hidden <en>feature does not exist and all users
address@hidden <en>can run @code{cvs admin}.
+O grupo @code{cvsadmin} deve existir no servidor, ou em
+qualquer sistemas rodando o ???não-cliente???/servidor
+do @sc{cvs}. Para desabilitar o @code{cvs admin} para
+todos os usuários, crie um grupo sem usuários nele. No
+NT, esta característica do @code{cvsadmin} não existe e
+todos os usuários podem rodar o @code{cvs admin}.
@menu
-* admin options:: admin options
address@hidden <en>* admin options:: admin options
+* Opções do admin:: Opções do admin
@end menu
@c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
address@hidden admin options
address@hidden admin options
-
address@hidden <en>@node admin options
address@hidden Opções do admin
address@hidden <en>@appendixsubsec admin options
address@hidden Opções do admin
+
address@hidden <en>Some of these options have questionable usefulness for
address@hidden <en>@sc{cvs} but exist for historical purposes. Some even
address@hidden <en>make it impossible to use @sc{cvs} until you undo the
address@hidden <en>effect!
Some of these options have questionable usefulness for
@sc{cvs} but exist for historical purposes. Some even
make it impossible to use @sc{cvs} until you undo the
effect!
@table @code
address@hidden <en>@item address@hidden
address@hidden <en>Might not work together with @sc{cvs}. Append the
address@hidden <en>access list of @var{oldfile} to the access list of the
address@hidden <en>@sc{rcs} file.
@item address@hidden
Might not work together with @sc{cvs}. Append the
access list of @var{oldfile} to the access list of the
@sc{rcs} file.
address@hidden <en>@item address@hidden
address@hidden <en>Might not work together with @sc{cvs}. Append the
address@hidden <en>login names appearing in the comma-separated list
address@hidden <en>@var{logins} to the access list of the @sc{rcs} file.
@item address@hidden
Might not work together with @sc{cvs}. Append the
login names appearing in the comma-separated list
@@ -13906,14 +13937,25 @@
@sc{rcs} 5.7. Therefore, you can almost surely not
worry about it. @xref{Substituição de palavra-chave}.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>Might not work together with @sc{cvs}. Erase the login
address@hidden <en>names appearing in the comma-separated list
address@hidden <en>@var{logins} from the access list of the RCS file. If
address@hidden <en>@var{logins} is omitted, erase the entire access list.
address@hidden <en>There can be no space between @samp{-e} and its argument.
Might not work together with @sc{cvs}. Erase the login
names appearing in the comma-separated list
@var{logins} from the access list of the RCS file. If
@var{logins} is omitted, erase the entire access list.
There can be no space between @samp{-e} and its argument.
address@hidden <en>@item -I
@item -I
address@hidden <en>Run interactively, even if the standard input is not a
address@hidden <en>terminal. This option does not work with the
address@hidden <en>client/server @sc{cvs} and is likely to disappear in
address@hidden <en>a future release of @sc{cvs}.
Run interactively, even if the standard input is not a
terminal. This option does not work with the
client/server @sc{cvs} and is likely to disappear in
@@ -13942,13 +13984,28 @@
@code{cvs update}, @code{cvs export}, or @code{cvs
checkout} overrides this default.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>Lock the revision with number @var{rev}. If a branch
address@hidden <en>is given, lock the latest revision on that branch. If
address@hidden <en>@var{rev} is omitted, lock the latest revision on the
address@hidden <en>default branch. There can be no space between
address@hidden <en>@samp{-l} and its argument.
Lock the revision with number @var{rev}. If a branch
is given, lock the latest revision on that branch. If
@var{rev} is omitted, lock the latest revision on the
default branch. There can be no space between
@samp{-l} and its argument.
address@hidden <en>This can be used in conjunction with the
address@hidden <en>@file{rcslock.pl} script in the @file{contrib}
address@hidden <en>directory of the @sc{cvs} source distribution to
address@hidden <en>provide reserved checkouts (where only one user can be
address@hidden <en>editing a given file at a time). See the comments in
address@hidden <en>that file for details (and see the @file{README} file
address@hidden <en>in that directory for disclaimers about the unsupported
address@hidden <en>nature of contrib). According to comments in that
address@hidden <en>file, locking must set to strict (which is the default).
This can be used in conjunction with the
@file{rcslock.pl} script in the @file{contrib}
directory of the @sc{cvs} source distribution to
@@ -13959,18 +14016,31 @@
nature of contrib). According to comments in that
file, locking must set to strict (which is the default).
address@hidden <en>@item -L
@item -L
address@hidden <en>Set locking to strict. Strict locking means that the
address@hidden <en>owner of an RCS file is not exempt from locking for
address@hidden <en>checkin. For use with @sc{cvs}, strict locking must be
address@hidden <en>set; see the discussion under the @samp{-l} option above.
Set locking to strict. Strict locking means that the
owner of an RCS file is not exempt from locking for
checkin. For use with @sc{cvs}, strict locking must be
set; see the discussion under the @samp{-l} option above.
address@hidden <en>@cindex Changing a log message
@cindex Changing a log message
address@hidden <en>@cindex Replacing a log message
@cindex Replacing a log message
address@hidden <en>@cindex Correcting a log message
@cindex Correcting a log message
address@hidden <en>@cindex Fixing a log message
@cindex Fixing a log message
address@hidden <en>@cindex Log message, correcting
@cindex Log message, correcting
address@hidden <en>@item address@hidden:@var{msg}
@item address@hidden:@var{msg}
address@hidden <en>Replace the log message of revision @var{rev} with
address@hidden <en>@var{msg}.
Replace the log message of revision @var{rev} with
@var{msg}.
@@ -13986,7 +14056,26 @@
assignment of @var{name}. For use with magic branches,
see @ref{Números de ramos mágicos}.
address@hidden <en>@item address@hidden:address@hidden
@item address@hidden:address@hidden
address@hidden <en>Associate the symbolic name @var{name} with the branch
address@hidden <en>or revision @var{rev}. It is normally better to use
address@hidden <en>@samp{cvs tag} or @samp{cvs rtag} instead. Delete the
address@hidden <en>symbolic name if both @samp{:} and @var{rev} are
address@hidden <en>omitted; otherwise, print an error message if
address@hidden <en>@var{name} is already associated with another number.
address@hidden <en>If @var{rev} is symbolic, it is expanded before
address@hidden <en>association. A @var{rev} consisting of a branch number
address@hidden <en>followed by a @samp{.} stands for the current latest
address@hidden <en>revision in the branch. A @samp{:} with an empty
address@hidden <en>@var{rev} stands for the current latest revision on the
address@hidden <en>default branch, normally the trunk. For example,
address@hidden <en>@samp{cvs admin address@hidden:} associates @var{name} with
the
address@hidden <en>current latest revision of all the RCS files;
address@hidden <en>this contrasts with @samp{cvs admin address@hidden:$} which
address@hidden <en>associates @var{name} with the revision numbers
address@hidden <en>extracted from keyword strings in the corresponding
address@hidden <en>working files.
Associate the symbolic name @var{name} with the branch
or revision @var{rev}. It is normally better to use
@samp{cvs tag} or @samp{cvs rtag} instead. Delete the
@@ -14006,18 +14095,37 @@
extracted from keyword strings in the corresponding
working files.
address@hidden <en>@cindex Deleting revisions
@cindex Deleting revisions
address@hidden <en>@cindex Outdating revisions
@cindex Outdating revisions
address@hidden <en>@cindex Saving space
@cindex Saving space
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>Deletes (@dfn{outdates}) the revisions given by
address@hidden <en>@var{range}.
Deletes (@dfn{outdates}) the revisions given by
@var{range}.
address@hidden <en>Note that this command can be quite dangerous unless
address@hidden <en>you know @emph{exactly} what you are doing (for example
address@hidden <en>see the warnings below about how the
address@hidden <en>@var{rev1}:@var{rev2} syntax is confusing).
Note that this command can be quite dangerous unless
you know @emph{exactly} what you are doing (for example
see the warnings below about how the
@var{rev1}:@var{rev2} syntax is confusing).
address@hidden <en>If you are short on disc this option might help you.
address@hidden <en>But think twice before using it---there is no way short
address@hidden <en>of restoring the latest backup to undo this command!
address@hidden <en>If you delete different revisions than you planned,
address@hidden <en>either due to carelessness or (heaven forbid) a @sc{cvs}
address@hidden <en>bug, there is no opportunity to correct the error
address@hidden <en>before the revisions are deleted. It probably would be
address@hidden <en>a good idea to experiment on a copy of the repository
address@hidden <en>first.
If you are short on disc this option might help you.
But think twice before using it---there is no way short
of restoring the latest backup to undo this command!
@@ -14028,10 +14136,22 @@
a good idea to experiment on a copy of the repository
first.
address@hidden <en>Specify @var{range} in one of the following ways:
Specify @var{range} in one of the following ways:
@table @code
address@hidden <en>@item @var{rev1}::@var{rev2}
@item @var{rev1}::@var{rev2}
address@hidden <en>Collapse all revisions between rev1 and rev2, so that
address@hidden <en>@sc{cvs} only stores the differences associated with going
address@hidden <en>from rev1 to rev2, not intermediate steps. For
address@hidden <en>example, after @samp{-o 1.3::1.5} one can retrieve
address@hidden <en>revision 1.3, revision 1.5, or the differences to get
address@hidden <en>from 1.3 to 1.5, but not the revision 1.4, or the
address@hidden <en>differences between 1.3 and 1.4. Other examples:
address@hidden <en>@samp{-o 1.3::1.4} and @samp{-o 1.3::1.3} have no
address@hidden <en>effect, because there are no intermediate revisions to
address@hidden <en>remove.
Collapse all revisions between rev1 and rev2, so that
@sc{cvs} only stores the differences associated with going
from rev1 to rev2, not intermediate steps. For
@@ -14043,7 +14163,14 @@
effect, because there are no intermediate revisions to
remove.
address@hidden <en>@item ::@var{rev}
@item ::@var{rev}
address@hidden <en>Collapse revisions between the beginning of the branch
address@hidden <en>containing @var{rev} and @var{rev} itself. The
address@hidden <en>branchpoint and @var{rev} are left intact. For
address@hidden <en>example, @samp{-o ::1.3.2.6} deletes revision 1.3.2.1,
address@hidden <en>revision 1.3.2.5, and everything in between, but leaves
address@hidden <en>1.3 and 1.3.2.6 intact.
Collapse revisions between the beginning of the branch
containing @var{rev} and @var{rev} itself. The
branchpoint and @var{rev} are left intact. For
@@ -14051,12 +14178,19 @@
revision 1.3.2.5, and everything in between, but leaves
1.3 and 1.3.2.6 intact.
address@hidden <en>@item @var{rev}::
@item @var{rev}::
address@hidden <en>Collapse revisions between @var{rev} and the end of the
address@hidden <en>branch containing @var{rev}. Revision @var{rev} is
address@hidden <en>left intact but the head revision is deleted.
Collapse revisions between @var{rev} and the end of the
branch containing @var{rev}. Revision @var{rev} is
left intact but the head revision is deleted.
address@hidden <en>@item @var{rev}
@item @var{rev}
address@hidden <en>Delete the revision @var{rev}. For example, @samp{-o
address@hidden <en>1.3} is equivalent to @samp{-o 1.2::1.4}.
Delete the revision @var{rev}. For example, @samp{-o
1.3} is equivalent to @samp{-o 1.2::1.4}.
@@ -14161,6 +14295,7 @@
a bogus commit; commit a new revision undoing the bogus
change instead (@pxref{Mesclando duas revisões}).
address@hidden <en>@item -q
@item -q
@c <en>Run quietly; do not print diagnostics.
Run quietly; do not print diagnostics.
@@ -14202,7 +14337,14 @@
commands like @code{cvs remove} and @code{cvs add}, not
@code{cvs admin -s}.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>Useful with @sc{cvs}. Write descriptive text from the
address@hidden <en>contents of the named @var{file} into the RCS file,
address@hidden <en>deleting the existing text. The @var{file} pathname
address@hidden <en>may not begin with @samp{-}. The descriptive text can be
seen in the
address@hidden <en>output from @samp{cvs log} (@pxref{log}).
address@hidden <en>There can be no space between @samp{-t} and its argument.
Useful with @sc{cvs}. Write descriptive text from the
contents of the named @var{file} into the RCS file,
deleting the existing text. The @var{file} pathname
@@ -14210,13 +14352,23 @@
output from @samp{cvs log} (@pxref{log}).
There can be no space between @samp{-t} and its argument.
address@hidden <en>If @var{file} is omitted,
address@hidden <en>obtain the text from standard input, terminated by
address@hidden <en>end-of-file or by a line containing @samp{.} by itself.
address@hidden <en>Prompt for the text if interaction is possible; see
address@hidden <en>@samp{-I}.
If @var{file} is omitted,
obtain the text from standard input, terminated by
end-of-file or by a line containing @samp{.} by itself.
Prompt for the text if interaction is possible; see
@samp{-I}.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>Similar to @address@hidden Write descriptive text
address@hidden <en>from the @var{string} into the @sc{rcs} file, deleting
address@hidden <en>the existing text.
address@hidden <en>There can be no space between @samp{-t} and its argument.
Similar to @address@hidden Write descriptive text
from the @var{string} into the @sc{rcs} file, deleting
the existing text.
@@ -14226,7 +14378,13 @@
@c minor changes, has never been documented as a
@c cvs admin option.
address@hidden <en>@item -U
@item -U
address@hidden <en>Set locking to non-strict. Non-strict locking means
address@hidden <en>that the owner of a file need not lock a revision for
address@hidden <en>checkin. For use with @sc{cvs}, strict locking must be
address@hidden <en>set; see the discussion under the @samp{-l} option
address@hidden <en>above.
Set locking to non-strict. Non-strict locking means
that the owner of a file need not lock a revision for
checkin. For use with @sc{cvs}, strict locking must be
@@ -14256,7 +14414,12 @@
notification (@pxref{Recebendo Notificações}).
There can be no space between @samp{-u} and its argument.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>In previous versions of @sc{cvs}, this option meant to
address@hidden <en>write an @sc{rcs} file which would be acceptable to
address@hidden <en>@sc{rcs} version @var{n}, but it is now obsolete and
address@hidden <en>specifying it will produce an error.
In previous versions of @sc{cvs}, this option meant to
write an @sc{rcs} file which would be acceptable to
@sc{rcs} version @var{n}, but it is now obsolete and
@@ -14264,7 +14427,13 @@
@c Note that -V without an argument has never been
@c documented as a cvs admin option.
address@hidden <en>@item address@hidden
@item address@hidden
address@hidden <en>In previous versions of @sc{cvs}, this was documented
address@hidden <en>as a way of specifying the names of the @sc{rcs}
address@hidden <en>files. However, @sc{cvs} has always required that the
address@hidden <en>@sc{rcs} files used by @sc{cvs} end in @samp{,v}, so
address@hidden <en>this option has never done anything useful.
In previous versions of @sc{cvs}, this was documented
as a way of specifying the names of the @sc{rcs}
files. However, @sc{cvs} has always required that the
@@ -16991,7 +17160,7 @@
@c <en>Delete revisions from the repository. See
@c <en>@ref{admin options}.
Delete revisions from the repository. See
address@hidden options}.
address@hidden do admin}.
@c <en>@item -q
@item -q
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Cvs-cvs] ccvs/doc/i18n/pt_BR cvs.texinfo,
Fred Ulisses Maranhão <=