[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Cvs-cvs] Changes to ccvs/doc/i18n/pt_BR/cvs.texinfo
|
From: |
Fred Ulisses Maranhão |
|
Subject: |
[Cvs-cvs] Changes to ccvs/doc/i18n/pt_BR/cvs.texinfo |
|
Date: |
Fri, 02 Sep 2005 23:13:41 -0400 |
Index: ccvs/doc/i18n/pt_BR/cvs.texinfo
diff -u ccvs/doc/i18n/pt_BR/cvs.texinfo:1.37
ccvs/doc/i18n/pt_BR/cvs.texinfo:1.38
--- ccvs/doc/i18n/pt_BR/cvs.texinfo:1.37 Thu Sep 1 13:48:59 2005
+++ ccvs/doc/i18n/pt_BR/cvs.texinfo Sat Sep 3 03:13:40 2005
@@ -11971,7 +11971,7 @@
@c <en>@chapter Tracking third-party sources
@chapter Tracking third-party sources
@c <en>@cindex Third-party sources
address@hidden Third-party sources
address@hidden Fontes de terceiros
@c <en>@cindex Tracking sources
@cindex Tracking sources
@@ -11989,15 +11989,17 @@
@c <en>probably want to include your modifications when the next
@c <en>release of the program arrives. @sc{cvs} can help you with
@c <en>this task.
-If you modify a program to better fit your site, you
-probably want to include your modifications when the next
-release of the program arrives. @sc{cvs} can help you with
-this task.
+Se você modificar um programa para se adequar melhor ao
+seu ambiente, você provavelmente vai querer incluir
+suas modificações quando a nova release do do programa
+chegar. O @sc{cvs} pode te ajudar nesta tarefa.
@c <en>@cindex Vendor
@cindex Vendor
address@hidden Vendor (fornecedor)
@c <en>@cindex Vendor branch
address@hidden Vendor branch
address@hidden Vendor branch (ramo do forncedor)
address@hidden Ramo do fornecedor
@c <en>@cindex Branch, vendor-
@cindex Branch, vendor-
@c <en>In the terminology used in @sc{cvs}, the supplier of the
@@ -12005,20 +12007,22 @@
@c <en>distribution from the vendor is checked in on its own
@c <en>branch, the @dfn{vendor branch}. @sc{cvs} reserves branch
@c <en>1.1.1 for this use.
-In the terminology used in @sc{cvs}, the supplier of the
-program is called a @dfn{vendor}. The unmodified
-distribution from the vendor is checked in on its own
-branch, the @dfn{vendor branch}. @sc{cvs} reserves branch
-1.1.1 for this use.
+Na terminologia usada no @sc{cvs}, quem fornece um
+programa é chamado de @dfn{vendor} (fornecedor, em
+português). A distribuição não modificada do
+fornecedor é ???checked in??? no seu próprio ramo, o
address@hidden branch} (ramo do fornecedor). O @sc{cvs}
+reserva o ramo 1.1.1 para isto.
@c <en>When you modify the source and commit it, your revision
@c <en>will end up on the main trunk. When a new release is
@c <en>made by the vendor, you commit it on the vendor branch
@c <en>and copy the modifications onto the main trunk.
-When you modify the source and commit it, your revision
-will end up on the main trunk. When a new release is
-made by the vendor, you commit it on the vendor branch
-and copy the modifications onto the main trunk.
+Quando você modifica a fonte e a ???commit???, sua
+revisão vai terminar na ???main trunk???. Quando uma
+nova release é feita pelo fornecedor, você ???commit???
+ela no ramo do fornecedor e copia as modificações no
+???main trunk???.
@c <en>Use the @code{import} command to create and update
@c <en>the vendor branch. When you import a new file,
@@ -12027,39 +12031,39 @@
@c <en>revision. When a local modification is committed it is
@c <en>placed on the main trunk, and made the `head'
@c <en>revision.
-Use the @code{import} command to create and update
-the vendor branch. When you import a new file,
-the vendor branch is made the `head' revision, so
-anyone that checks out a copy of the file gets that
-revision. When a local modification is committed it is
-placed on the main trunk, and made the `head'
-revision.
+Use o comando @code{import} para criar e atualizar o
+ramo do fornecedor. Quando você importa um novo
+arquivo, o ramo do fornecedor se torna a revisão
+`head', logo qualquer um que ???checks out??? uma cópia
+do arquivo pega esta revisão. Quando uma modificação
+local é ???committed???, ela é posta no ???main
+trunk???, e se torna a revisão `head'.
@menu
@c <en>* First import:: Importing for the first time
-* First import:: Importing for the first time
+* Primeira importação:: Importando pela primeira vez
@c <en>* Update imports:: Updating with the import command
-* Update imports:: Updating with the import command
+* Importações de atualização:: Atualizando com o comando import
@c <en>* Reverting local changes:: Reverting to the latest vendor release
-* Reverting local changes:: Reverting to the latest vendor release
+* Reverting local changes:: Reverting to the latest vendor release
@c <en>* Binary files in imports:: Binary files require special handling
-* Binary files in imports:: Binary files require special handling
+* Arquivos binários em importações:: Arquivos binários requerem tratamento
especial
@c <en>* Keywords in imports:: Keyword substitution might be
undesirable
-* Keywords in imports:: Keyword substitution might be undesirable
+* Palavras-chave em importações:: Substituição de palavras-chave pode
ser indesejável
@c <en>* Multiple vendor branches:: What if you get sources from several
places?
-* Multiple vendor branches:: What if you get sources from several places?
+* Ramos de fornecedor múltiplos:: E se você obtém fontes de vários
lugares?
@end menu
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@c <en>@node First import
address@hidden First import
address@hidden Primeira importação
@c <en>@section Importing for the first time
@section Importing for the first time
@c <en>@cindex Importing modules
@cindex Importing modules
address@hidden <en>@c Should mention naming conventions for vendor tags,
address@hidden <en>@c release tags, and perhaps directory names.
address@hidden Should mention naming conventions for vendor tags,
address@hidden release tags, and perhaps directory names.
@c <en>Use the @code{import} command to check in the sources
@c <en>for the first time. When you use the @code{import}
@c <en>command to track third-party sources, the @dfn{vendor
@@ -12069,15 +12073,13 @@
@c <en>@var{branch}} flag---see @ref{Multiple vendor branches}.). The
@c <en>@dfn{release tags} are symbolic names for a particular
@c <en>release, such as @samp{FSF_0_04}.
address@hidden Should mention naming conventions for vendor tags,
address@hidden release tags, and perhaps directory names.
Use the @code{import} command to check in the sources
for the first time. When you use the @code{import}
command to track third-party sources, the @dfn{vendor
tag} and @dfn{release tags} are useful. The
@dfn{vendor tag} is a symbolic name for the branch
(which is always 1.1.1, unless you use the @samp{-b
address@hidden flag---see @ref{Multiple vendor branches}.). The
address@hidden flag---see @ref{Ramos de fornecedor múltiplos}.). The
@dfn{release tags} are symbolic names for a particular
release, such as @samp{FSF_0_04}.
@@ -12127,7 +12129,7 @@
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@c <en>@node Update imports
address@hidden Update imports
address@hidden Importações de atualização
@c <en>@section Updating with the import command
@section Updating with the import command
@@ -12146,6 +12148,10 @@
$ cvs import -m "Import of FSF v. 0.05" fsf/wdiff FSF_DIST WDIFF_0_05
@end example
address@hidden <en>For files that have not been modified locally, the newly
created
address@hidden <en>revision becomes the head revision. If you have made local
address@hidden <en>changes, @code{import} will warn you that you must merge the
changes
address@hidden <en>into the main trunk, and tell you to use @samp{checkout -j}
to do so:
For files that have not been modified locally, the newly created
revision becomes the head revision. If you have made local
changes, @code{import} will warn you that you must merge the changes
@@ -12171,6 +12177,8 @@
the merge they should be resolved in the normal way
(@pxref{Exemplo de conflitos}). Then, the modified files may be committed.
address@hidden <en>However, it is much better to use the two release tags
rather than using
address@hidden <en>a date on the branch as suggested above:
However, it is much better to use the two release tags rather than using
a date on the branch as suggested above:
@@ -12179,6 +12187,13 @@
@end example
@noindent
address@hidden <en>The reason this is better is that
address@hidden <en>using a date, as suggested above, assumes that you do
address@hidden <en>not import more than one release of a product per day.
address@hidden <en>More importantly, using the release tags allows @sc{cvs} to
detect files
address@hidden <en>that were removed between the two vendor releases and mark
them for
address@hidden <en>removal. Since @code{import} has no way to detect removed
files, you
address@hidden <en>should do a merge like this even if @code{import} doesn't
tell you to.
The reason this is better is that
using a date, as suggested above, assumes that you do
not import more than one release of a product per day.
@@ -12187,9 +12202,18 @@
removal. Since @code{import} has no way to detect removed files, you
should do a merge like this even if @code{import} doesn't tell you to.
address@hidden <en>@node Reverting local changes
@node Reverting local changes
address@hidden <en>@section Reverting to the latest vendor release
@section Reverting to the latest vendor release
address@hidden <en>You can also revert local changes completely and return
address@hidden <en>to the latest vendor release by changing the `head'
address@hidden <en>revision back to the vendor branch on all files. For
address@hidden <en>example, if you have a checked-out copy of the sources
address@hidden <en>in @file{~/work.d/wdiff}, and you want to revert to the
address@hidden <en>vendor's version for all the files in that directory,
address@hidden <en>you would type:
You can also revert local changes completely and return
to the latest vendor release by changing the `head'
revision back to the vendor branch on all files. For
@@ -12204,17 +12228,25 @@
@end example
@noindent
address@hidden <en>You must specify the @samp{-bFSF_DIST} without any space
address@hidden <en>after the @samp{-b}. @xref{admin options}.
You must specify the @samp{-bFSF_DIST} without any space
after the @samp{-b}. @xref{admin options}.
address@hidden Binary files in imports
address@hidden <en>@node Binary files in imports
address@hidden Arquivos binários em importações
address@hidden <en>@section How to handle binary files with cvs import
@section How to handle binary files with cvs import
address@hidden <en>Use the @samp{-k} wrapper option to tell import which
address@hidden <en>files are binary. @xref{Wrappers}.
Use the @samp{-k} wrapper option to tell import which
files are binary. @xref{Wrappers}.
address@hidden Keywords in imports
address@hidden How to handle keyword substitution with cvs import
address@hidden <en>@node Keywords in imports
address@hidden Palavras-chave em importações
address@hidden <en>@section How to handle keyword substitution with cvs import
address@hidden Como lidar com substituição de palavras-chave com o cvs import
@c <en>The sources which you are importing may contain
@c <en>keywords (@pxref{Keyword substitution}). For example,
@@ -12239,6 +12271,14 @@
that this information can supply information about
the sources that you imported from the vendor.
address@hidden <en>To maintain the keyword expansions supplied by the
address@hidden <en>vendor, supply the @samp{-ko} option to @code{cvs
address@hidden <en>import} the first time you import the file.
address@hidden <en>This will turn off keyword expansion
address@hidden <en>for that file entirely, so if you want to be more
address@hidden <en>selective you'll have to think about what you want
address@hidden <en>and use the @samp{-k} option to @code{cvs update} or
address@hidden <en>@code{cvs admin} as appropriate.
To maintain the keyword expansions supplied by the
vendor, supply the @samp{-ko} option to @code{cvs
import} the first time you import the file.
@@ -12251,9 +12291,21 @@
@c has no effect. Not clear to me whether it should
@c or not.
address@hidden Multiple vendor branches
address@hidden Multiple vendor branches
-
address@hidden <en>@node Multiple vendor branches
address@hidden Ramos de fornecedor múltiplos
address@hidden <en>@section Multiple vendor branches
address@hidden Ramos de fornecedor múltiplos
+
address@hidden <en>All the examples so far assume that there is only one
address@hidden <en>vendor from which you are getting sources. In some
address@hidden <en>situations you might get sources from a variety of
address@hidden <en>places. For example, suppose that you are dealing with
address@hidden <en>a project where many different people and teams are
address@hidden <en>modifying the software. There are a variety of ways to
address@hidden <en>handle this, but in some cases you have a bunch of
address@hidden <en>source trees lying around and what you want to do more
address@hidden <en>than anything else is just to all put them in @sc{cvs} so
address@hidden <en>that you at least have them in one place.
All the examples so far assume that there is only one
vendor from which you are getting sources. In some
situations you might get sources from a variety of
@@ -12265,11 +12317,21 @@
than anything else is just to all put them in @sc{cvs} so
that you at least have them in one place.
address@hidden <en>For handling situations in which there may be more than
address@hidden <en>one vendor, you may specify the @samp{-b} option to
address@hidden <en>@code{cvs import}. It takes as an argument the vendor
address@hidden <en>branch to import to. The default is @samp{-b 1.1.1}.
For handling situations in which there may be more than
one vendor, you may specify the @samp{-b} option to
@code{cvs import}. It takes as an argument the vendor
branch to import to. The default is @samp{-b 1.1.1}.
address@hidden <en>For example, suppose that there are two teams, the red
address@hidden <en>team and the blue team, that are sending you sources.
address@hidden <en>You want to import the red team's efforts to branch
address@hidden <en>1.1.1 and use the vendor tag RED. You want to import
address@hidden <en>the blue team's efforts to branch 1.1.3 and use the
address@hidden <en>vendor tag BLUE. So the commands you might use are:
For example, suppose that there are two teams, the red
team and the blue team, that are sending you sources.
You want to import the red team's efforts to branch
@@ -12291,6 +12353,11 @@
@end example
@noindent
address@hidden <en>Be careful; this kind of mismatch is sure to sow
address@hidden <en>confusion or worse. I can't think of a useful purpose
address@hidden <en>for the ability to specify a mismatch here, but if you
address@hidden <en>discover such a use, don't. @sc{cvs} is likely to make this
address@hidden <en>an error in some future release.
Be careful; this kind of mismatch is sure to sow
confusion or worse. I can't think of a useful purpose
for the ability to specify a mismatch here, but if you
@@ -12309,11 +12376,19 @@
@c to figure out builds right away. The current location
@c is based on the theory that it kind of akin to the
@c "Revision management" section.
address@hidden <en>@node Builds
@node Builds
address@hidden <en>@chapter How your build system interacts with CVS
@chapter How your build system interacts with CVS
address@hidden <en>@cindex Builds
@cindex Builds
address@hidden <en>@cindex make
@cindex make
address@hidden <en>As mentioned in the introduction, @sc{cvs} does not
address@hidden <en>contain software for building your software from source
address@hidden <en>code. This section describes how various aspects of
address@hidden <en>your build system might interact with @sc{cvs}.
As mentioned in the introduction, @sc{cvs} does not
contain software for building your software from source
code. This section describes how various aspects of
@@ -12323,6 +12398,26 @@
@c tools other than CVS? I'm not sure there is; I
@c wouldn't think that people who learn CVS first would
@c even have this concern.
address@hidden <en>One common question, especially from people who are
address@hidden <en>accustomed to @sc{rcs}, is how to make their build get
address@hidden <en>an up to date copy of the sources. The answer to this
address@hidden <en>with @sc{cvs} is two-fold. First of all, since
address@hidden <en>@sc{cvs} itself can recurse through directories, there
address@hidden <en>is no need to modify your @file{Makefile} (or whatever
address@hidden <en>configuration file your build tool uses) to make sure
address@hidden <en>each file is up to date. Instead, just use two
address@hidden <en>commands, first @code{cvs -q update} and then
address@hidden <en>@code{make} or whatever the command is to invoke your
address@hidden <en>build tool. Secondly, you do not necessarily
address@hidden <en>@emph{want} to get a copy of a change someone else made
address@hidden <en>until you have finished your own work. One suggested
address@hidden <en>approach is to first update your sources, then
address@hidden <en>implement, build and
address@hidden <en>test the change you were thinking of, and then commit
address@hidden <en>your sources (updating first if necessary). By
address@hidden <en>periodically (in between changes, using the approach
address@hidden <en>xjust described) updating your entire tree, you ensure
address@hidden <en>that your sources are sufficiently up to date.
One common question, especially from people who are
accustomed to @sc{rcs}, is how to make their build get
an up to date copy of the sources. The answer to this
@@ -12344,6 +12439,7 @@
just described) updating your entire tree, you ensure
that your sources are sufficiently up to date.
address@hidden <en>@cindex Bill of materials
@cindex Bill of materials
@c <en>One common need is to record which versions of which
@c <en>source files went into a particular build. This kind
@@ -12360,6 +12456,13 @@
record which versions went into a given build
(@pxref{Etiquetas}).
address@hidden <en>Using @sc{cvs} in the most straightforward manner
address@hidden <en>possible, each developer will have a copy of the entire
address@hidden <en>source tree which is used in a particular build. If
address@hidden <en>the source tree is small, or if developers are
address@hidden <en>geographically dispersed, this is the preferred
address@hidden <en>solution. In fact one approach for larger projects is
address@hidden <en>to break a project down into smaller
Using @sc{cvs} in the most straightforward manner
possible, each developer will have a copy of the entire
source tree which is used in a particular build. If
@@ -12369,11 +12472,19 @@
to break a project down into smaller
@c I say subsystem instead of module because they may or
@c may not use the modules file.
address@hidden <en>separately-compiled subsystems, and arrange a way of
address@hidden <en>releasing them internally so that each developer need
address@hidden <en>check out only those subsystems which they are
address@hidden <en>actively working on.
separately-compiled subsystems, and arrange a way of
releasing them internally so that each developer need
check out only those subsystems which they are
actively working on.
address@hidden <en>Another approach is to set up a structure which allows
address@hidden <en>developers to have their own copies of some files, and
address@hidden <en>for other files to access source files from a central
address@hidden <en>location. Many people have come up with some such a
Another approach is to set up a structure which allows
developers to have their own copies of some files, and
for other files to access source files from a central
@@ -12384,6 +12495,12 @@
@c but as far as I know
@c no one has nicely packaged or released such a system (or
@c instructions for constructing one).
address@hidden <en>system using features such as the symbolic link feature
address@hidden <en>found in many operating systems, or the @code{VPATH}
address@hidden <en>feature found in many versions of @code{make}. One build
address@hidden <en>tool which is designed to help with this kind of thing
address@hidden <en>is Odin (see
address@hidden <en>@code{ftp://ftp.cs.colorado.edu/pub/distribs/odin}).
system using features such as the symbolic link feature
found in many operating systems, or the @code{VPATH}
feature found in many versions of @code{make}. One build
@@ -12426,6 +12543,16 @@
@c <en>@cindex Symbolic links
@cindex Symbolic links
address@hidden <en>In normal circumstances, @sc{cvs} works only with regular
address@hidden <en>files. Every file in a project is assumed to be
address@hidden <en>persistent; it must be possible to open, read and close
address@hidden <en>them; and so on. @sc{cvs} also ignores file permissions and
address@hidden <en>ownerships, leaving such issues to be resolved by the
address@hidden <en>developer at installation time. In other words, it is
address@hidden <en>not possible to "check in" a device into a repository;
address@hidden <en>if the device file cannot be opened, @sc{cvs} will refuse to
address@hidden <en>handle it. Files also lose their ownerships and
address@hidden <en>permissions during repository transactions.
In normal circumstances, @sc{cvs} works only with regular
files. Every file in a project is assumed to be
persistent; it must be possible to open, read and close
@@ -12519,17 +12646,20 @@
@end ignore
@c ---------------------------------------------------------------------
address@hidden <en>@node Comandos do CVS
@node Comandos do CVS
address@hidden <en>@appendix Guia dos comandos do CVS
@appendix Guia dos comandos do CVS
@c <en>This appendix describes the overall structure of
@c <en>@sc{cvs} commands, and describes some commands in
@c <en>detail (others are described elsewhere; for a quick
@c <en>reference to @sc{cvs} commands, @pxref{Invoking CVS}).
-This appendix describes the overall structure of
address@hidden commands, and describes some commands in
-detail (others are described elsewhere; for a quick
-reference to @sc{cvs} commands, @pxref{Chamando o CVS}).
+Este apêndice descreve a estrutura geral dos comandos
+do @sc{cvs}, e descreve alguns comandos em detalhe
+(outros são descritos em outra parte; para
+uma referência rápida dos comandos do @sc{cvs},
address@hidden o CVS}).
@c The idea is that we want to move the commands which
@c are described here into the main body of the manual,
@c in the process reorganizing the manual to be
@@ -12547,107 +12677,160 @@
@menu
@c <en>* Structure:: Overall structure of CVS commands
-* Structure:: Overall structure of CVS commands
+* Estrutura:: Estrutura geral dos comandos do CVS
@c <en>* Exit status:: Indicating CVS's success or failure
-* Exit status:: Indicating CVS's success or failure
+* Estados de saída:: Indicando o sucesso ou falha do CVS
@c <en>* ~/.cvsrc:: Default options with the ~/.cvsrc file
-* ~/.cvsrc:: Default options with the ~/.cvsrc file
+* ~/.cvsrc:: Opções padrão com o arquivo ~/.cvsrc
@c <en>* Global options:: Options you give to the left of
cvs_command
-* Opções globais:: Options you give to the left of cvs_command
+* Opções globais:: Opções que você bota a esquerda do
comando_do_cvs
@c <en>* Common options:: Options you give to the right of
cvs_command
-* Opções comuns:: Options you give to the right of cvs_command
+* Opções comuns:: Opções que você bota a direita do comando_do_cvs
@c <en>* admin:: Administration
-* admin:: Administration
+* admin:: Administração
@c <en>* checkout:: Checkout sources for editing
-* checkout:: Checkout sources for editing
+* checkout:: ???Checkout??? fontes para edição
@c <en>* commit:: Check files into the repository
-* commit:: Check files into the repository
+* commit:: Colocar arquivos no repositório
@c <en>* diff:: Show differences between revisions
-* diff:: Show differences between revisions
+* diff:: Mostrar diferenças entre revisões
@c <en>* export:: Export sources from CVS, similar to
checkout
-* export:: Export sources from CVS, similar to checkout
+* export:: Exportar fontes para fora do CVS, similar ao
???checkout???
@c <en>* history:: Show status of files and users
-* history:: Show status of files and users
+* history:: Mostrar estado de arquivos e usuários
@c <en>* import:: Import sources into CVS, using vendor
branches
-* import:: Import sources into CVS, using vendor branches
+* import:: Importar fontes para dentro do CVS, usando
ramos de fornecedor
@c <en>* log:: Show log messages for files
-* log:: Show log messages for files
+* log:: Mostrar mensagens de log para arquivos
@c <en>* rdiff:: 'patch' format diffs between releases
* rdiff:: 'patch' format diffs between releases
@c <en>* release:: Indicate that a directory is no longer
in use
-* release:: Indicate that a directory is no longer in use
+* release:: Avisar que um diretorio não está mais em uso
@c <en>* update:: Bring work tree in sync with repository
-* update:: Bring work tree in sync with repository
+* update:: Deixar árvore de trabalho em sincronia com o
repositório
@end menu
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
address@hidden Structure
address@hidden Overall structure of CVS commands
address@hidden Structure
address@hidden CVS command structure
address@hidden Command structure
address@hidden Format of CVS commands
address@hidden <en>@node Structure
address@hidden Estrutura
address@hidden <en>@appendixsec Overall structure of CVS commands
address@hidden Estrutura geral dos comandos do CVS
address@hidden <en>@cindex Structure
address@hidden Estrutura
address@hidden <en>@cindex CVS command structure
address@hidden Estrutura do comando CVS
address@hidden <en>@cindex Command structure
address@hidden Estrutura do comando
address@hidden <en>@cindex Format of CVS commands
address@hidden Formato dos comandos do CVS
-The overall format of all @sc{cvs} commands is:
address@hidden <en>The overall format of all @sc{cvs} commands is:
+O formato geral de todos os comandos do @sc{cvs} é:
@example
cvs [ cvs_options ] cvs_command [ command_options ] [ command_args ]
@end example
@table @code
address@hidden <en>@item cvs
@item cvs
-The name of the @sc{cvs} program.
address@hidden <en>The name of the @sc{cvs} program.
+O nome do programa @sc{cvs}.
address@hidden <en>@item cvs_options
@item cvs_options
-Some options that affect all sub-commands of @sc{cvs}. These are
-described below.
address@hidden <en>Some options that affect all sub-commands of @sc{cvs}.
These are
address@hidden <en>described below.
+Algumas opções que afetam todos os sub-comandos do
address@hidden Estes estão descritos abaixo.
address@hidden <en>@item cvs_command
@item cvs_command
-One of several different sub-commands. Some of the commands have
-aliases that can be used instead; those aliases are noted in the
-reference manual for that command. There are only two situations
-where you may omit @samp{cvs_command}: @samp{cvs -H} elicits a
-list of available commands, and @samp{cvs -v} displays version
-information on @sc{cvs} itself.
address@hidden <en>One of several different sub-commands. Some of the commands
have
address@hidden <en>aliases that can be used instead; those aliases are noted in
the
address@hidden <en>reference manual for that command. There are only two
situations
address@hidden <en>where you may omit @samp{cvs_command}: @samp{cvs -H} elicits
a
address@hidden <en>list of available commands, and @samp{cvs -v} displays
version
address@hidden <en>information on @sc{cvs} itself.
+Um dos vários sub-comandos. Alguns dos comandos têm
+???aliases??? substituí-los; estes ???aliases??? são
+listados no manual de referência do comando. Existem
+apenas duas situações onde você pode omitir o
address@hidden: @samp{cvs -H} retorna uma lista de
+comandos disponíveis, e @samp{cvs -v} mostra
+informações sobre a versão do próprio @sc{cvs}.
address@hidden <en>@item command_options
@item command_options
-Options that are specific for the command.
address@hidden <en>Options that are specific for the command.
+Opções que são específicas para o comando.
address@hidden <en>@item command_args
@item command_args
-Arguments to the commands.
address@hidden <en>Arguments to the commands.
+Argumentos para os comandos.
@end table
-There is unfortunately some confusion between
address@hidden and @code{command_options}.
address@hidden, when given as a @code{cvs_option}, only
-affects some of the commands. When it is given as a
address@hidden is has a different meaning, and
-is accepted by more commands. In other words, do not
-take the above categorization too seriously. Look at
-the documentation instead.
-
address@hidden Exit status
address@hidden CVS's exit status
address@hidden Exit status, of CVS
-
address@hidden can indicate to the calling environment whether it
-succeeded or failed by setting its @dfn{exit status}.
-The exact way of testing the exit status will vary from
-one operating system to another. For example in a unix
-shell script the @samp{$?} variable will be 0 if the
-last command returned a successful exit status, or
-greater than 0 if the exit status indicated failure.
-
-If @sc{cvs} is successful, it returns a successful status;
-if there is an error, it prints an error message and
-returns a failure status. The one exception to this is
-the @code{cvs diff} command. It will return a
-successful status if it found no differences, or a
-failure status if there were differences or if there
-was an error. Because this behavior provides no good
-way to detect errors, in the future it is possible that
address@hidden diff} will be changed to behave like the
-other @sc{cvs} commands.
address@hidden <en>There is unfortunately some confusion between
address@hidden <en>@code{cvs_options} and @code{command_options}.
address@hidden <en>@samp{-l}, when given as a @code{cvs_option}, only
address@hidden <en>affects some of the commands. When it is given as a
address@hidden <en>@code{command_option} is has a different meaning, and
address@hidden <en>is accepted by more commands. In other words, do not
address@hidden <en>take the above categorization too seriously. Look at
address@hidden <en>the documentation instead.
+Infelizmente, existe alguma confusão entre
address@hidden e @code{command_options}. @samp{-l},
+quando passado como @code{cvs_option}, afeta apenas
+alguns dos comandos. Quando é passado como um
address@hidden tem um significado diferente, e é
+aceito por mais comandos. Em outras palavras, não leve
+a categorização acima tão a sério. Olhe a
+documentação, ao invés disto.
+
address@hidden <en>@node Exit status
address@hidden Estados de saída
address@hidden <en>@appendixsec CVS's exit status
address@hidden estado de saída do CVS
address@hidden <en>@cindex Exit status, of CVS
address@hidden Estados de saída do CVS
+
address@hidden <en>@sc{cvs} can indicate to the calling environment whether it
address@hidden <en>succeeded or failed by setting its @dfn{exit status}.
address@hidden <en>The exact way of testing the exit status will vary from
address@hidden <en>one operating system to another. For example in a unix
address@hidden <en>shell script the @samp{$?} variable will be 0 if the
address@hidden <en>last command returned a successful exit status, or
address@hidden <en>greater than 0 if the exit status indicated failure.
+O @sc{cvs} pode indicar para o ambiente que o chamou se
+ele foi bem-sucedido ou falhou ao ajustar seu
address@hidden de saída}. A forma exata de testar o
+estado de saída varia de um sistema operacional para
+outro. Por exemplo, num shell script do unix a
+variável @samp{$?} será 0 se o último comando retornar
+um estado de saída bem-sucedido, ou maior que 0 se o
+estado de saída indicar uma falha.
+
address@hidden <en>If @sc{cvs} is successful, it returns a successful status;
address@hidden <en>if there is an error, it prints an error message and
address@hidden <en>returns a failure status. The one exception to this is
address@hidden <en>the @code{cvs diff} command. It will return a
address@hidden <en>successful status if it found no differences, or a
address@hidden <en>failure status if there were differences or if there
address@hidden <en>was an error. Because this behavior provides no good
address@hidden <en>way to detect errors, in the future it is possible that
address@hidden <en>@code{cvs diff} will be changed to behave like the
address@hidden <en>other @sc{cvs} commands.
+Se o @sc{cvs} é bem-sucedido, retorna um estado de sucesso;
+se existe um erro, mostra uma mensagem de erro e
+retorna um estado de falha. A única exceção para isto
+é o comando @code{cvs diff}. Ele retornará um estado
+de sucesso se não encontrar diferenças, ou um estado de
+sucesso se existirem diferenças ou acontecer um erro.
+Já que este comportamento não fornece uma boa maneira
+de detectar erros, é possível que no futuro o @code{cvs
+diff} seja mudado para se comportar como os outros
+comandos do @sc{cvs}.
@c It might seem like checking whether cvs -q diff
@c produces empty or non-empty output can tell whether
@c there were differences or not. But it seems like
@@ -12661,37 +12844,65 @@
@c bring back (but what does it mean for VMS?)?
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
address@hidden <en>@node ~/.cvsrc
@node ~/.cvsrc
address@hidden Default options and the ~/.cvsrc file
address@hidden .cvsrc file
address@hidden Option defaults
-
-There are some @code{command_options} that are used so
-often that you might have set up an alias or some other
-means to make sure you always specify that option. One
-example (the one that drove the implementation of the
address@hidden support, actually) is that many people find the
-default output of the @samp{diff} command to be very
-hard to read, and that either context diffs or unidiffs
-are much easier to understand.
-
-The @file{~/.cvsrc} file is a way that you can add
-default options to @code{cvs_commands} within cvs,
-instead of relying on aliases or other shell scripts.
-
-The format of the @file{~/.cvsrc} file is simple. The
-file is searched for a line that begins with the same
-name as the @code{cvs_command} being executed. If a
-match is found, then the remainder of the line is split
-up (at whitespace characters) into separate options and
-added to the command arguments @emph{before} any
-options from the command line.
-
-If a command has two names (e.g., @code{checkout} and
address@hidden), the official name, not necessarily the one
-used on the command line, will be used to match against
-the file. So if this is the contents of the user's
address@hidden/.cvsrc} file:
address@hidden <en>@appendixsec Default options and the ~/.cvsrc file
address@hidden Opções padrão e o arquivo ~/.cvsrc
address@hidden <en>@cindex .cvsrc file
address@hidden Arquivo .cvsrc
address@hidden <en>@cindex Option defaults
address@hidden Padrão, opções
+
address@hidden <en>There are some @code{command_options} that are used so
address@hidden <en>often that you might have set up an alias or some other
address@hidden <en>means to make sure you always specify that option. One
address@hidden <en>example (the one that drove the implementation of the
address@hidden <en>@file{.cvsrc} support, actually) is that many people find the
address@hidden <en>default output of the @samp{diff} command to be very
address@hidden <en>hard to read, and that either context diffs or unidiffs
address@hidden <en>are much easier to understand.
+Existem algumas @code{opções_de_comando} que são tão
+usadas que você vai querer preparar um atalho ou
+alguma outra forma de ter certeza que tais opções
+sempre vão ser especificadas. Um exemplo (o que
+motivou a implementação do suporte ao arquivo
address@hidden, na verdade) é que muitas pessoas acham a
+saída do comando @samp{diff} muito difícil de ler, e
+que tanto diffs de contexto quanto unidiffs são muito
+mais fáceis de entender.
+
address@hidden <en>The @file{~/.cvsrc} file is a way that you can add
address@hidden <en>default options to @code{cvs_commands} within cvs,
address@hidden <en>instead of relying on aliases or other shell scripts.
+O arquivo @file{~/.cvsrc} é uma forma de você adicionar
+opções padrão aos @code{comandos_cvs} dentro do cvs, ao
+invés de usar alias (apelidos) ou outros scripts de shell.
+
address@hidden <en>The format of the @file{~/.cvsrc} file is simple. The
address@hidden <en>file is searched for a line that begins with the same
address@hidden <en>name as the @code{cvs_command} being executed. If a
address@hidden <en>match is found, then the remainder of the line is split
address@hidden <en>up (at whitespace characters) into separate options and
address@hidden <en>added to the command arguments @emph{before} any
address@hidden <en>options from the command line.
+O formato do arquivo @file{~/.cvsrc} é simples. O
+arquivo é varrido por uma linha que comece com o mesmo
+nome do @code{comando_cvs} sendo executado. Se
+encontra, então o restante da linha é dividido (pelos
+espaços) em opções distintas e adicionadas aos
+argumentos do comando @emph{antes} de quaisquer opções
+da linha de comando.
+
address@hidden <en>If a command has two names (e.g., @code{checkout} and
address@hidden <en>@code{co}), the official name, not necessarily the one
address@hidden <en>used on the command line, will be used to match against
address@hidden <en>the file. So if this is the contents of the user's
address@hidden <en>@file{~/.cvsrc} file:
+Se um comando tem dois nomes (e.g., @code{checkout} e
address@hidden), o nome oficial, que não é necessariamente o
+usado na linha de comando, vai ser usado para fazer a
+busca no arquivo. Logo, se este é o conteúdo do
+arquivo @file{~/.cvsrc} do usuário:
@example
log -N
@@ -12703,31 +12914,42 @@
@end example
@noindent
-the command @samp{cvs checkout foo} would have the
address@hidden option added to the arguments, as well as
address@hidden <en>the command @samp{cvs checkout foo} would have the
address@hidden <en>@samp{-P} option added to the arguments, as well as
address@hidden <en>@samp{cvs co foo}.
+o comando @samp{cvs checkout foo} vai ter a opção
address@hidden adicionada a seus argumentos, assim como
@samp{cvs co foo}.
-With the example file above, the output from @samp{cvs
-diff foobar} will be in unidiff format. @samp{cvs diff
--c foobar} will provide context diffs, as usual.
-Getting "old" format diffs would be slightly more
-complicated, because @code{diff} doesn't have an option
-to specify use of the "old" format, so you would need
address@hidden -f diff foobar}.
address@hidden <en>With the example file above, the output from @samp{cvs
address@hidden <en>diff foobar} will be in unidiff format. @samp{cvs diff
address@hidden <en>-c foobar} will provide context diffs, as usual.
address@hidden <en>Getting "old" format diffs would be slightly more
address@hidden <en>complicated, because @code{diff} doesn't have an option
address@hidden <en>to specify use of the "old" format, so you would need
address@hidden <en>@samp{cvs -f diff foobar}.
+Com o arquivo de exemplo acima, a saída de @samp{cvs
+diff foobar} vai ser no formato unidiff. @samp{cvs
+diff -c foobar} vai dar diffs de contexto, que é o normal.
+Obter o diff no formato "velho" vai ser um pouco mais
+complicado, já que o @code{diff} não tem uma opção para
+especificar o uso do formato "velho", logo você vai ter
+que usar @samp{cvs -f diff foobar}.
@c <en>In place of the command name you can use @code{cvs} to
@c <en>specify global options (@pxref{Global options}). For
@c <en>example the following line in @file{.cvsrc}
-In place of the command name you can use @code{cvs} to
-specify global options (@pxref{Opções globais}). For
-example the following line in @file{.cvsrc}
+Ao invés de no nome do comando você pode usar o
address@hidden especificando opções globais (@pxref{Opções globais}). Por
+exemplo a seguinte linha em @file{.cvsrc}
@example
cvs -z6
@end example
@noindent
-causes @sc{cvs} to use compression level 6.
address@hidden <en>causes @sc{cvs} to use compression level 6.
+faz com que o @sc{cvs} use compressão de nível 6.
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@c <en>@node Global options
@@ -14355,8 +14577,10 @@
compared. If any directories are given, all files
under them will be compared.
address@hidden <en>The exit status for diff is different than for other
address@hidden <en>@sc{cvs} commands; for details @ref{Exit status}.
The exit status for diff is different than for other
address@hidden commands; for details @ref{Exit status}.
address@hidden commands; for details @ref{Estados de saída}.
@menu
* diff options:: diff options
@@ -15358,8 +15582,10 @@
There are the following additional special options.
@table @code
address@hidden <en>@item -b @var{branch}
@item -b @var{branch}
-See @ref{Multiple vendor branches}.
address@hidden <en>See @ref{Multiple vendor branches}.
+See @ref{Ramos de fornecedor múltiplos}.
@c <en>@item -k @var{subst}
@item -k @var{subst}
@@ -17068,7 +17294,7 @@
@c <en>Import to vendor branch @var{bra}. See
@c <en>@ref{Multiple vendor branches}.
Import to vendor branch @var{bra}. See
address@hidden vendor branches}.
address@hidden de fornecedor múltiplos}.
@c <en>@item -d
@item -d