summaryrefslogtreecommitdiffstats
path: root/common/cvs-it.xml
diff options
context:
space:
mode:
authorFrancesco Tombolini <tombo@adamantio.net>2005-11-20 18:29:38 +0000
committerFrancesco Tombolini <tombo@adamantio.net>2005-11-20 18:29:38 +0000
commitf05ea3bc2b5e5d49c3bf66ad64ae2b09b4ef9af5 (patch)
tree71b38c6ba10ea4834f85ab05a2d4e49517b578d4 /common/cvs-it.xml
parentea0b1952a971222148358de8ec563cbe96e7c33f (diff)
downloadfedora-doc-utils-f05ea3bc2b5e5d49c3bf66ad64ae2b09b4ef9af5.tar.gz
fedora-doc-utils-f05ea3bc2b5e5d49c3bf66ad64ae2b09b4ef9af5.tar.xz
fedora-doc-utils-f05ea3bc2b5e5d49c3bf66ad64ae2b09b4ef9af5.zip
Translation complete
Diffstat (limited to 'common/cvs-it.xml')
-rw-r--r--common/cvs-it.xml569
1 files changed, 284 insertions, 285 deletions
diff --git a/common/cvs-it.xml b/common/cvs-it.xml
index 37ebb96..a2e70a7 100644
--- a/common/cvs-it.xml
+++ b/common/cvs-it.xml
@@ -293,17 +293,17 @@ update -dP</computeroutput></screen>
<secondary>accesso anonimo</secondary>
</indexterm>
<para>
- If your goal is to download the various &FC; documents and to
- render them on your system, you only need read-only access to
- the <application>CVS</application> repository. Follow the
- instructions in this section and then skip directly to
+ Se il tuo obbiettivo è scaricare i vari documenti &FC; e
+ renderizzarli sul tuo sistema, hai bisogno solo di un accesso read-only
+ al depositorio <application>CVS</application>. Segui le
+ instruzioni in questa sezione quindi salta direttamente a
<xref linkend="sn-cvs-cvscommands-co"/>.
</para>
<para>
- Change directories to where you want your files from
- <application>CVS</application> to be located, and execute the
- following commands:
+ Cambia directories dove vuoi che vengano collocati i files dal
+ <application>CVS</application>, ed esegui i
+ seguenti comandi:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>cvs login</command>
@@ -311,204 +311,204 @@ update -dP</computeroutput></screen>
<prompt>$ </prompt><command>cvs checkout</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cd</command> <replaceable>module-name</replaceable></screen>
<para>
- Once you have checked the module out, it doesn't matter what
- your
+ Una volta eseguito il check-out del modulo, non importa quale
<envar>CVSROOT</envar>
- is set to because it is stored in the file
- <filename>CVS/Root</filename> for each directory in your local
- repository. As long as your current working directory has a
- <filename>CVS/</filename> directory, the
- <application>CVS</application> program will automatically locate
- the &FC; repository.
+ è impostata perchè è registrata nel file
+ <filename>CVS/Root</filename> per ogni directory nel tuo depositorio
+ locale. Finchè la tua directory di lavoro ha una directory
+ <filename>CVS/</filename>, il programma
+ <application>CVS</application> localizzerà automaticamente
+ il repositorio &FC;.
</para>
</section>
<section id="sn-cvs-config-author">
- <title>Configuring Read/Write CVS Access</title>
+ <title>Configurazione accesso CVS Read/Write</title>
<indexterm>
<primary>cvs</primary>
- <secondary>configuring read/write access</secondary>
+ <secondary>configurazione accesso read/write</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
- <secondary>configuring access for authors</secondary>
+ <secondary>configurare gli accessi per gli autori</secondary>
</indexterm>
<para>
- To author a new document or to change an existing one, you must
- obtain full read/write access to the &FC; Docs
- <application>CVS</application> repository. For the full details
- on this process, refer to the
+ Per scrivere un nuovo documento o modificarne uno esistente, devi
+ ottenere pieno accesso read/write al repositorio
+ <application>CVS</application> della Documentazione di &FC;.
+ Per i dettagli completi su questo procedimento, fa riferimento al
+ sito web
<ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename>
- </ulink> web site. Below is a summary:
+ </ulink>. Segue un sommario:
</para>
<itemizedlist>
<listitem>
<para>
- Subscribe to the
+ Sotoscriviti alla
<ulink url="https://listman.redhat.com/mailman/listinfo/fedora-docs-list"><filename>fedora-docs-list</filename>
- </ulink>, which is the main forum for the project.
+ </ulink>, che è il forum principale del progetto.
</para>
</listitem>
<listitem>
<para>
- Generate a GNU Privacy Guard (<abbrev>GPG</abbrev>) key to
- identify yourself to the project.
+ Genera una chiave GNU Privacy Guard (<abbrev>GPG</abbrev>) per
+ identificarti nel progetto.
</para>
</listitem>
<listitem>
<para>
- Register for a
+ Registrati per un account in
<ulink url="http://bugzilla.redhat.com/"><filename>Bugzilla</filename>
- </ulink> account, if you do not have one already.
- <filename>Bugzilla</filename> is how we keep track of bugs,
- changes and projects.
+ </ulink>, se non ne hai già uno.
+ <filename>Bugzilla</filename> è il modo con cui teniamo traccia degli errori,
+ cambiamenti e progetti.
</para>
</listitem>
<listitem>
<para>
- Post a
- <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
- introduction</ulink> to the list.
+ Posta un
+ <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+ introduzione</ulink> alla lista.
</para>
</listitem>
</itemizedlist>
<para>
- After your
- <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
- introduction</ulink> has been approved your
- <application>CVS</application> access will be granted.
+ Dopo che la tua
+ <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+ introduzione</ulink> è stata approvata il tuo accesso
+ <application>CVS</application> verrà garantito.
</para>
<para>
- Every author, and that includes you once your self introduction
- has been received, has a unique
+ Ogni autore, e questo ti include una volta che la tua auto introduzione
+ è stat ricevuta, ha un unico
<envar>$CVSROOT</envar>
- to access the <application>CVS</application> repository:
+ per accedere al repositorio <application>CVS</application>:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:ext:</command><replaceable>yourname</replaceable><command>@cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>export CVS_RSH=/usr/bin/ssh</command></screen>
<para>
- With the
+ Con le variabili ambiente
<envar>$CVSROOT</envar>
- and
+ e
<envar>$CVS_RSH</envar>
- environment variables in place, you can access the repository:
+ impostate, puoi accedera al repositorio:
</para>
<screen><prompt>$ </prompt><command>cvs co -c</command></screen>
<para>
- You will be asked for the passphrase for your
- <application>SSH</application> key. Press
+ Ti verrà richiesta la passphrase per la tua chiave
+ <application>SSH</application>. Premi
<guibutton>ENTER</guibutton>
- and you should receive a list of modules already in the
- repository.
+ e riceverai la lista dei moduli presenti nel
+ repositorio.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands">
- <title>Basic CVS Commands</title>
+ <title>Comandi CVS di base</title>
<indexterm>
<primary>cvs</primary>
- <secondary>commands</secondary>
+ <secondary>comandi</secondary>
</indexterm>
<para>
- After configuring your system to work with CVS, checkout the
- modules you will be working on.
+ Dopo aver configurato il sistema per funzionare con CVS, esegui il checkout
+ dei moduli su cui lavorerai.
</para>
<tip>
<title>Tip</title>
<para>
- To see if you need a correctly-set
- <envar>$CVSROOT</envar>
- variable, or the <option>-m </option>
- <replaceable>repository</replaceable> command line switch, see
- if you have a <filename>CVS/</filename> subdirectory in your
- working directory.
+ Per vedere se hai impostato correttamente la variabile
+ <envar>$CVSROOT</envar>,
+ o lo switch della linea di comando <option>-m </option>
+ <replaceable>repository</replaceable>, vedi
+ se hai una subdirectory <filename>CVS/</filename> nella tua
+ directory di lavoro.
</para>
<para>
- If you have a <filename>CVS/</filename> directory,
- <application>CVS</application> ignores any
+ Se hai una directory <filename>CVS/</filename>,
+ <application>CVS</application> ignorera qualsiasi
<envar>$CVSROOT</envar>
- or <option>-m</option> command line switch.
+ o switch della linea di comando <option>-m</option>.
</para>
</tip>
<section id="sn-cvs-cvscommands-co">
- <title>Checking Out Modules</title>
+ <title>Fare il checkout dei moduli</title>
<indexterm>
<primary>cvs</primary>
- <secondary>checking out modules</secondary>
+ <secondary>eseguire il checkout dei moduli</secondary>
</indexterm>
<para>
- You only need to checkout a module once. After a local copy of
- the module is on your system, it is on your system.
+ Devi fare il checkout di un modulo una volta. Dopo che la copia del
+ modulo è sul tuo sistema, è sul tuo sistema.
</para>
<para>
- To checkout a module, use the following command:
+ Per fare il checkout di un modulo, usa il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <replaceable>&lt;module-name&gt;</replaceable></screen>
<para>
- For example, to checkout the
- <computeroutput>example-tutorial</computeroutput> module, change
- to your work directory, and execute the following command:
+ Per esempio, per fare il checkout del modulo
+ <computeroutput>example-tutorial</computeroutput>, cambia
+ la tua directory di lavoro, ed esegui il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
<para>
- A directory called <filename>example-tutorial/</filename> is
- created in the current directory.
+ Verrà creata una directory chiamata <filename>example-tutorial/</filename>
+ nela directory corrente.
</para>
<para>
- If a branch name is not specified when checking out a module, it
- is referred to as the <firstterm>HEAD</firstterm> of the
- <application>CVS</application> module.
+ Se non viene specificato un nome del ramo durante il checking del modulo,
+ verrà riferito al <firstterm>HEAD</firstterm> del modulo
+ <application>CVS</application>.
</para>
<section id="sn-cvs-cvscommands-co-branch">
- <title>Checking Out Branches of Modules</title>
+ <title>Fare il checkout dei rami dei moduli</title>
<indexterm>
<primary>cvs</primary>
- <secondary>check out modules</secondary>
- <tertiary>checking out branches</tertiary>
+ <secondary>eseguire il checkout dei moduli</secondary>
+ <tertiary>eseguire il checkout dei rami</tertiary>
</indexterm>
<para>
- Think of a <application>CVS</application> branch as a version
- of the files for a particular version of a manual or package.
+ Pensa ad un ramo <application>CVS</application> come una versione
+ dei files per una particolare versione del pacchetto o manuale.
</para>
<para>
- To checkout a branch of a module, use the following command:
+ Per fare il checkout di un ramo di un modulo, usa il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <option>-d</option> <replaceable>&lt;directory&gt;</replaceable> <option>-r</option> <replaceable>&lt;branchname&gt;</replaceable> <replaceable>&lt;module-name&gt;</replaceable></screen>
<para>
- A directory named <replaceable>&lt;directory&gt;</replaceable>
- is created, and the files for the
- <replaceable>&lt;branchname&gt;</replaceable> branch of the
- <replaceable>&lt;module-name&gt;</replaceable> module are
- copied in the directory.
+ Una directory chiamata <replaceable>&lt;directory&gt;</replaceable>
+ viene creata, ed i files per il ramo
+ <replaceable>&lt;branchname&gt;</replaceable> del modulo
+ <replaceable>&lt;module-name&gt;</replaceable> sono
+ copiati nella directory.
</para>
<para>
- For example, to checkout a branch named BRANCH-VERSION-1.2
- from the <computeroutput>mymodule</computeroutput> module, use
- the command:
+ Per esempio, per fare il checkout di un ramo denominato BRANCH-VERSION-1.2
+ dal modulo <computeroutput>mymodule</computeroutput>, usa
+ il comando:
</para>
<screen><prompt>$ </prompt><command>cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule</command></screen>
<para>
- The BRANCH-VERSION-1.2 branch of the module is checked out in
- the <filename>mymodule-1.2</filename> directory on your
- system.
+ Verrà eseguito il checkout del ramo BRANCH-VERSION-1.2 del modulo nella
+ directory <filename>mymodule-1.2</filename> sul tuo
+ sistema.
</para>
<para>
- To determine which branches and tags exist for a file, use the
- command:
+ Per determinare quale ramo e tags esiste per un file, usa il
+ comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <option>-v</option> <replaceable>&lt;filename&gt;</replaceable></screen>
<para>
- For example, the status of the file
- <filename>foo.sgml</filename> is as follows:
+ Per esempio, lo status del file
+ <filename>foo.sgml</filename> è il seguente:
</para>
<screen>
<computeroutput>
@@ -526,207 +526,206 @@ File: foo.sgml Status: Up-to-date
</computeroutput>
</screen>
<para>
- Only tags marked as branches in the second column under the
- <computeroutput>Existing Tags</computeroutput> section can be
- checked out as a branch.
+ Solo dei tags marcati come rami nella seconda colonna sotto la
+ sezione <computeroutput>Existing Tags</computeroutput> si può eseguire
+ il checkout come ramo.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands-up">
- <title>Updating Files</title>
+ <title>Aggiornare i files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>updating files</secondary>
+ <secondary>aggiornare i files</secondary>
</indexterm>
<para>
- To retrieve the latest versions of the files in a module, change
- to the directory that contains the files for the module and
- execute the command:
+ Per ricevere l'ultima versione di un file in un modulo, cambia
+ nella directory che contiene i files per il modulo ed
+ esegui il comando:
</para>
<screen><command>cvs update</command></screen>
<para>
- The latest versions of all the files in the module are
- downloaded into your local copy. If you notice a file conflict,
- refer to <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
+ Le ultime versioni di tutti i files ne modulo sono
+ scaricate nella tua copia locale. Se noti un conflitto di file,
+ fa riferimento a <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-commit">
- <title>Committing Files</title>
+ <title>Eseguire il commit dei files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>committing files</secondary>
+ <secondary>eseguire il commit dei files</secondary>
</indexterm>
<para>
- After modifying files in your local version of a module, commit
- them to save the changes on the <application>CVS</application>
+ Dopo aver modificato i files nella tua versione locale di un modulo, esegui il commit
+ per salvare i cambiamenti sul <application>CVS</application>
server:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>filename</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>alcuni messaggi di log</replaceable>&quot; <replaceable>filename</replaceable></screen>
<note>
<para>
- If you would prefer to write your log message with your
- favorite text editor, as defined by the $VISUAL or the $EDITOR
- environment variable, just omit the <userinput>-m &quot;some
- log message&quot;</userinput>. The buffer will already contain
- comments describing the change; you do not need to delete them
- as you enter your own text.
+ Se preferisci scrivere il tuo messaggio di log con il tuo editor
+ di testo preferito, come definito dalla variabile ambiente $VISUAL o
+ $EDITOR, ometti semplicemente la <userinput>-m &quot;alcuni
+ messaggi di log&quot;</userinput>. Il buffer conterrà già
+ alcuni commenti che descrivono i cambiamenti; non è necessario cancellarli
+ quando inserirai il tuo testo.
</para>
</note>
<para>
- The log message should be as descriptive as possible so that you
- and anyone else working on the module understands what changed.
- Using a log message such as <userinput>updated some
- files</userinput> does not accurately describe what has changed
- and will not help you in the future. If you are correcting a
- bug, use the <application>Bugzilla</application> reference.
+ I messaggi di log dovranno essere più descrittivi possibile affinchè
+ chiunque altro lavori al modulo capisca cos'è stato cambiato.
+ Usare un messaggio di log tipo <userinput>aggiornati alcuni
+ files</userinput> non descrive accuratamente cosa è stato cambiato
+ e non ti aiuterà in futuro. Se hai corretto un
+ errore, fa riferimento a <application>Bugzilla</application>.
</para>
<para>
- The <replaceable>&lt;filename&gt;</replaceable> can be one
- filename, a series of filenames separated by spaces, or a group
- of filenames specified using wildcards such as
- <filename>*.png</filename> or <filename>foo-*.sgml</filename>.
+ Il <replaceable>&lt;filename&gt;</replaceable> può essere un
+ filename, una serie si filenames separati da spazi, o un gruppo
+ di filenames specificati usando una wildcards tipo
+ <filename>*.png</filename> o <filename>foo-*.sgml</filename>.
</para>
<para>
- If no filename or group of filenames is specified in the
- <command>commit</command> command, all outstanding changes of
- any kind are committed to the server. The command is recursive
- and will include changes in any subdirectories of the module.
- Use caution when issuing the <command>commit</command> command
- without any filenames because you might not remember exactly
- what files changed.
+ Se nessun filename o gruppo di filenames è specificato nel
+ comando <command>commit</command>, tutti i cambiamenti eccezionali
+ di qualsiasi tipo sono commessi al server. Il comando è recursivo
+ ed includerà i cambiamenti in ogni subdirectories del modulo.
+ Usa cautela qunado esegui il comando <command>commit</command>
+ senza nessun filenames poichè potresti non ricordare esattamente
+ quali files sono cambiano.
</para>
<para>
- If you notice a file conflict, refer to
+ Se noti un conflitto di file, fa riferimento a
<xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-add">
- <title>Adding Files</title>
+ <title>Aggiungere files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>adding files</secondary>
+ <secondary>aggiungere files</secondary>
</indexterm>
<para>
- To add a file to a module, create the file in your local copy
- then execute the following command:
+ Per aggiungere un file ad un modulo, crea il file sulla tua copia locale
+ quindi esegui il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs add</command> <replaceable>file-to-add</replaceable></screen>
<para>
- After adding the file, you must <command>commit</command> the
- <command>add</command> to copy it to the server:
+ Dopo aver aggiunto il file, devi eseguire un <command>commit</command>
+ dell'<command>add</command> per copiarlo sul server:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-add</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>qualche messaggio di log</replaceable>&quot; <replaceable>file-da-aggiungere</replaceable></screen>
</section>
<section id="sn-cvs-cvscommands-admin">
- <title>Managing Binary Files</title>
+ <title>Amministrare i files binari</title>
<indexterm>
<primary>cvs</primary>
- <secondary>binary files</secondary>
+ <secondary>files binari</secondary>
</indexterm>
<para>
- The most commonly-archived files are simple text files but
- sometimes binary files are also archived. The
- <application>cvs</application> program recognizes most common
- filename extentions such as <filename>.png</filename> or
- <filename>.jpg</filename>, so <application>cvs</application>
- usually &quot;does the right thing&quot;.
+ I files comunemente più archiviati sono di semplice testo ma
+ qualche volta sono archiviati anche files binari. Il programma
+ <application>cvs</application> determina le estensioni dei
+ files più comuni tipo <filename>.png</filename> o
+ <filename>.jpg</filename>, così di solito <application>cvs</application>
+ &quot;fa la cosa giusta&quot;.
</para>
<para>
- When a copy of a file is checked out of the repository,
- <application>cvs</application> scans it for special keywords,
- such as &quot;<computeroutput>$id:$</computeroutput>&quot; and
- replaces the string with a generated value, such as the file
- version number.
+ Quando si esegue il checkout della copia di un file del repositorio,
+ il <application>cvs</application> lo scansisce per parole chiavi speciali,
+ tipo &quot;<computeroutput>$id:$</computeroutput>&quot; e
+ sostituisce le stringhe con un valore generato, tipo il numero di versione
+ del file.
</para>
<para>
- This keyword substitution usually corrupts binary files, so it
- must be turned off if <application>cvs</application> does not
- recognize your file as binary. To mark your file as being
- binary, and thus needing the keyword expansion turned off, use
- the command:
+ Questa sostituzione di keyword di solito corrompe i files binari, così
+ deve essere disattivata se <application>cvs</application> non
+ reconosce i tuoi files come binari. Per marcare il tuo file come
+ binario, e quindi disattivare l'espansione dell keyword, usa
+ il comando:
</para>
<screen width="60"><prompt>$ </prompt><command>cvs</command> <option>admin</option> <option>-kk</option> <replaceable>filename</replaceable></screen>
<para>
- Note that the file must already be checked in to the
- <abbrev>CVS</abbrev> repository before the
- <option>admin</option> command can be used. This is OK, since
- the keyword expansion is done as the file is checked out and
- copied to the local directory, not when the file is committed to
- the repository.
+ Nota che il file deve già essere nel repositorio
+ <abbrev>CVS</abbrev> prima di poter usare il comando
+ <option>admin</option>. Questo è OK, fino a che
+ l'espansione delle keyword è fatta appena il file viene sottoposto a checkout e
+ copiato nella directory locale, non quando il file viene commesso al
+ repositorio.
</para>
<tip>
- <title>Recovering a binary file</title>
+ <title>Ripristinare un file binario</title>
<para>
- If you check a binary file into the repository and then find
- it corrupted when it is checked out, do not panic. Simply use
- the <option>admin</option> command as described above, delete
- your local file copy, and check it out again.
+ Se esegui il check di un file binario nel repositorio e trovi
+ che sia corrotto durante il checkout, non aver paura. Usa semplicemente
+ il comando <option>admin</option> come descritto sopra, cancella
+ la tua copia locale del file, ed esegui nuovamente il checkout.
</para>
</tip>
</section>
<section id="sn-cvs-cvscommands-rm">
- <title>Removing Files</title>
+ <title>Rimuovere i files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>removing files</secondary>
+ <secondary>rimuovere i files</secondary>
</indexterm>
<para>
- If a file is no longer needed in the module, use the
- <command>remove</command> command to remove it from your local
- copy and then <command>commit</command> the removal to the
- server. Even though the file is removed from current version of
- the module, an archived copy is still kept on the server and can
- be retrieved at any time with the <command>add</command>
- command.
+ Se un file non è più necessario nel modulo, usa il
+ comando <command>remove</command> per rimuoverlo dalla tua copia
+ locale poi esegui il <command>commit</command> per rimuoverlo dal
+ server. Anche se il file è rimosso dalla versione corrente del
+ modulo, una copia archiviata è ancora lasciata sul server e può
+ essere recuperato in qualsiasi momento con il comando <command>add</command>.
</para>
<screen><prompt>$ </prompt><command>cvs rm -f</command> <replaceable>file-to-remove</replaceable></screen>
<para>
- After removing the file, you must <command>commit</command> the
- removal:
+ Dopo la rimozione del file, devi eseguire il <command>commit</command> della
+ rimozione:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>&quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-remove</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>&quot;<replaceable>qualche messagiio di log</replaceable>&quot; <replaceable>file-da-rimuovere</replaceable></screen>
<para>
- You can not use wildcards in the <command>commit</command>
- command to identify removed files. They must be specified with a
- exact filename.
+ Non puoi usare wildcards nel eseguire il <command>commit</command>
+ per identificare files rimossi. Essi devono essere specificati con il nome
+ di file esatto.
</para>
<para>
- If you need to rename a file, it is best to rename the file on
- the <application>CVS</application> server so that the history of
- the file is preserved. If you need to rename a file, send an
- email to
+ Se necessiti di rinominare un file, è meglio rinominarlo sul
+ <application>CVS</application> server affinchè la storia del
+ file possa essere preservata. Se hai bisogno di rinominare un file, manda un
+ email a
<ulink url="mailto:cvsdocs-administrator@fedora.redhat.com"><filename>cvsdocs-administrator@fedora.redhat.com</filename>
- </ulink> asking to have the file renamed.
+ </ulink> chiedendo di voler rinominare un file.
</para>
</section>
<section id="sn-cvs-cvscommands-status">
- <title>Status of Files</title>
+ <title>Status dei files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>status of files</secondary>
+ <secondary>status dei files</secondary>
</indexterm>
<para>
- Sometimes it is necessary to view the
- <firstterm>status</firstterm> of a file in a
- <application>CVS</application> module. To view the status of a
- file, use the command:
+ Qualche volta è necessario vedere lo
+ <firstterm>status</firstterm> di un file in un
+ modulo <application>CVS</application>. Per vedere lo status di un
+ file, usa il comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <replaceable>filename</replaceable></screen>
<para>
- The status report of a repository file is as follows:
+ Il rapporto dello status di un file nel repositorio è come segue:
</para>
<variablelist>
@@ -734,8 +733,8 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Up-to-date</computeroutput></term>
<listitem>
<para>
- Your revision of the file is identical to the latest
- revision on the <application>CVS</application> server.
+ La tua revisione del file è identica all'ultima
+ revisione sul <application>CVS</application> server.
</para>
</listitem>
</varlistentry>
@@ -744,8 +743,8 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Locally Modified</computeroutput></term>
<listitem>
<para>
- You have updated to the latest revision from the server,
- but then you modified the file on your system.
+ Hai aggiornato il file all'ultima versione dal server,
+ ma poi hai modificatio il file sul tuo sistema.
</para>
</listitem>
</varlistentry>
@@ -754,8 +753,8 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Locally Added</computeroutput></term>
<listitem>
<para>
- You added the file with the <command>cvs add</command>
- command but have not yet committed the addition of the
+ Hai aggiunto il file con il comando <command>cvs add</command>
+ ma non hai ancora eseguito il commit per l'aggiunta del
file.
</para>
</listitem>
@@ -765,9 +764,9 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Locally Removed</computeroutput></term>
<listitem>
<para>
- You removed the file with the <command>cvs
- remove</command> command but have not yet committed the
- removal.
+ Hai rimosso il file con il comando <command>cvs
+ remove</command> ma non hai ancora eseguito il commit per la
+ rimozione.
</para>
</listitem>
</varlistentry>
@@ -776,10 +775,10 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Needs Checkout</computeroutput></term>
<listitem>
<para>
- A newer version of the file is on the server and needs to
- be retrieved. Even though the status includes the word
- checkout, it really means that you need to update your
- files with the <command>cvs update</command> command.
+ Sul server c'è una nuova versione del file ed necessita di
+ essere recuperata. Anche se lo status include la parola
+ checkout, vuoldire che hai bisogno di aggiornare
+ i files con il comando <command>cvs update</command>.
</para>
</listitem>
</varlistentry>
@@ -788,9 +787,9 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Needs Patch</computeroutput></term>
<listitem>
<para>
- The revision in your local checkout needs a patch to be
- the latest revision from the server. Issue the
- <command>cvs update</command> command to resolve.
+ La revisione del tuo checkout locale necessita di una patch per
+ essere l'ultima versione dal server. Esegui il
+ comando <command>cvs update</command> per risolvere.
</para>
</listitem>
</varlistentry>
@@ -799,10 +798,10 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Needs Merge</computeroutput></term>
<listitem>
<para>
- A newer revision exists on the server and your local
- version contains modification not yet committed. This
- status usually occurs if you don't have the latest
- revision of the file and edit it anyway.
+ Esiste una nuova revisione sul server e la tua versione di copia
+ locale contiene modifiche di cui non hai fatto ancora il commit. Questo
+ status di solito avviene se non hai l'ultima revisione
+ del file ed lo editi lo stesso.
</para>
</listitem>
</varlistentry>
@@ -811,12 +810,12 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>File had conflicts on merge</computeroutput></term>
<listitem>
<para>
- Similar to <computeroutput>Needs Merge</computeroutput>,
- except when you tried to issue the <command>cvs
- update</command> command, the differences could not be
- resolved automatically. Refer to
- <xref linkend="sn-cvs-cvscommands-conflicts"></xref> for
- more information on resolving conflicts.
+ Simile a <computeroutput>Needs Merge</computeroutput>,
+ eccetto che quando hai provato ad eseguire il comando <command>cvs
+ update</command>, le differenze non potevano essere
+ risolte automaticamente. Fa riferimento a
+ <xref linkend="sn-cvs-cvscommands-conflicts"></xref> per
+ maggiori informazioni sulla risoluzione dei conflitti.
</para>
</listitem>
</varlistentry>
@@ -825,14 +824,14 @@ File: foo.sgml Status: Up-to-date
<term><computeroutput>Unknown</computeroutput></term>
<listitem>
<para>
- The <application>CVS</application> server does not know
- anything about this file. It has neither been added nor
- removed locally and has never been committed to the
- server. This status usually occurs for files you should
- not commit to <application>CVS</application> such as
- <filename>generated-index.sgml</filename> or for files
- that you want to add to the repository but have not yet
- issued the <command>cvs add</command> command.
+ Il <application>CVS</application> server non sa nulla
+ su questo file. Il file non è stato aggiunto ne
+ rimosso loclamente e non è mai stato commesso al
+ server. Questo status di solito sussiste per i files che di cui non
+ vorresti fare il commit al <application>CVS</application> tipo
+ i <filename>generated-index.sgml</filename> o per quei files
+ che vorresti aggiungere al repositorio ma dei quali non hai
+ ancora impartito il comando <command>cvs add</command>.
</para>
</listitem>
</varlistentry>
@@ -840,16 +839,16 @@ File: foo.sgml Status: Up-to-date
</section>
<section id="sn-cvs-cvscommands-conflicts">
- <title>Resolving Conflicts</title>
+ <title>Risoluzione dei conflitti</title>
<indexterm>
<primary>cvs</primary>
- <secondary>resolving conflicts</secondary>
+ <secondary>risoluzione dei conflitti</secondary>
</indexterm>
<para>
- If you modify a file and the same region is modified by someone
- else and committed first, you will probably see a message
- similar to the following when committing the file or updating
- your local copy of the module:
+ Se modifichi un file e la stessa regione è modificata da qualcun'altro
+ che esegue il commitprima di te, probabilmente vedrai un messaggio
+ simile al seguente quando eseguirai il commit o l'aggiornamento
+ della tua copia locale del modulo:
</para>
<screen>
<computeroutput>
@@ -863,10 +862,10 @@ C filename.sgml
</computeroutput>
</screen>
<para>
- To resolve the conflict, open the file, search for
+ Per risolvere il conflitto, apri il file, cerca
<computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>
- and determine which version of the content is correct. For
- example:
+ e determina quale versione del contenuto è corretta. Per
+ esempio:
</para>
<screen>
<computeroutput>
@@ -881,40 +880,40 @@ A same sentence that was changed differently and committed.
</computeroutput>
</screen>
<para>
- The content between the
+ Il contenuto fra le
<computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>,
- and the <computeroutput>=======</computeroutput> is the content
- from your working copy. The content between the
- <computeroutput>=======</computeroutput> and the
- <computeroutput>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</computeroutput> is
- the content from the server.
+ e le <computeroutput>=======</computeroutput> è il contenuto
+ della tua copia di lavoro. Il contenuto fra le
+ <computeroutput>=======</computeroutput> e le
+ <computeroutput>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</computeroutput> è
+ il contenuto dal server.
</para>
<para>
- Resolve the conflict by editing your copy, and commit the file.
+ Resolvi il conflitto editando la tua copia, ed esegui il commit del file.
</para>
</section>
<section id="sn-cvs-cvscommands-summary">
- <title>Summary</title>
+ <title>Sommario</title>
<indexterm>
<primary>cvs</primary>
- <secondary>commands</secondary>
- <tertiary>summary of</tertiary>
+ <secondary>comandi</secondary>
+ <tertiary>sommario di</tertiary>
</indexterm>
<para>
- All commands assume you are in the proper directory for the
- <application>CVS</application> module.
+ Tutti i comandi assumono che tu sia nella directory appropriata per
+ il modulo <application>CVS</application>.
</para>
<table frame="all" id="tb-cvs-basic-commands">
- <title>Basic CVS Commands</title>
+ <title>Comandi CVS di base</title>
<tgroup cols="2">
<colspec colnum="1" colname="shortcut" colwidth="30"/>
<colspec colnum="2" colname="description" colwidth="60"/>
<thead>
<row>
- <entry>Command</entry>
- <entry>Description</entry>
+ <entry>Commando</entry>
+ <entry>Descrizione</entry>
</row>
</thead>
<tbody>
@@ -923,87 +922,87 @@ A same sentence that was changed differently and committed.
<replaceable>&lt;module-name&gt;</replaceable></command>
or <command>cvs co <replaceable>&lt;module-name&gt;</replaceable></command>
</entry>
- <entry>Creates a directory called
- <replaceable>&lt;module-name&gt;</replaceable> with the contents of the
- module in the directory</entry>
+ <entry>Crea una directory chiamata
+ <replaceable>&lt;module-name&gt;</replaceable> con il contenuto del
+ modulo nella directory</entry>
</row>
<row>
<entry><command>cvs co -d <replaceable>&lt;directory&gt;</replaceable> -r <replaceable>&lt;branchname&gt;</replaceable><replaceable>&lt;module-name&gt;</replaceable></command>
</entry>
- <entry>Creates the <replaceable>&lt;directory&gt;</replaceable> directory
- with the contents of the <replaceable>&lt;branchname&gt;</replaceable>
- branch of the <replaceable>&lt;module-name&gt;</replaceable> module</entry>
+ <entry>Crea la directory <replaceable>&lt;directory&gt;</replaceable>
+ con i contenuti del ramo <replaceable>&lt;branchname&gt;</replaceable>
+ del modulo <replaceable>&lt;module-name&gt;</replaceable></entry>
</row>
<row>
<entry><command>cvs update</command> or <command>cvs up</command>
</entry>
- <entry>Update your files with the latest files from the CVS server</entry>
+ <entry>Aggiorna i tuoi files con gli ultimi files dal CVS server</entry>
</row>
<row>
<entry><command>cvs add <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>Add a new file "filename" to the CVS server</entry>
+ <entry>Aggiunge un nuovo file "filename" al CVS server</entry>
</row>
<row>
<entry><command>cvs commit -m "My message"
<replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>Update file <replaceable>&lt;filename&gt;</replaceable> with the
- latest copy from your computer</entry>
+ <entry>Aggiorna il file <replaceable>&lt;filename&gt;</replaceable> con
+ l'ultima copia proveniente dal tuo computer</entry>
</row>
<row>
<entry><command>cvs log <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>View the commit messages for the file <replaceable>&lt;filename&gt;</replaceable>
+ <entry>Mostra i messaggi di commit per il file <replaceable>&lt;filename&gt;</replaceable>
</entry>
</row>
<row>
<entry><command>cvs status <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>View status of the file, such as <computeroutput>Locally
+ <entry>Mostra lo status del file, tipo <computeroutput>Locally
Modified</computeroutput>
</entry>
</row>
<row>
<entry><command>cvs status -v <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>View existing tags and branches for file</entry>
+ <entry>Mostra i tags esistenti ed i rami per il file</entry>
</row>
<row>
<entry><command>cvs diff <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>Show diff of the working copy of the file and the latest
- version of the file for the branch</entry>
+ <entry>Mostra la differenza della copia di lavoro del file e l'ultima
+ versione del file per il ramo</entry>
</row>
<row>
<entry><command>cvs diff -r1.1 -r1.2 <replaceable>&lt;filename&gt;</replaceable></command>
</entry>
- <entry>Show diff of version 1.1 and 1.2 for file</entry>
+ <entry>Mostra la differenza fra le versioni 1.1 e 1.2 per il file</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
- For more information, read the CVS manual available on your
- system at
+ Per maggiori informazioni, leggi il manuale CVS disponibile sul tuo
+ sistema in
<filename>/usr/share/doc/cvs-<replaceable>&lt;version-number&gt;</replaceable>/cvs.ps</filename>
- (the CVS version might vary) and visit the CVS webpage available
- at
+ (la versione CVS può cambiare) e visita la pagian web di CVS disponibile
+ su
<ulink url="http://www.cvshome.org/">http://www.cvshome.org/</ulink>.
</para>
<tip>
<title>Tip</title>
<para>
- Since <application>CVS</application> is using
- <application>ssh</application> to connect to the
- <application>CVS</application> server, you will be prompted
- your password before performing your
- <application>CVS</application> request. If you want to
- configure your machine so that you do not have to enter a
- password, refer to the
+ Poichè <application>CVS</application> usa
+ <application>ssh</application> per connettersi al
+ <application>CVS</application> server, ti verrà richiesta
+ la password prima di eseguire una richiesta
+ <application>CVS</application>. Se vuoi configurare
+ la tua macchina affinchè tu non abbia più bisogno di
+ inserire la password, fa riferimento a
<ulink url="http://redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-openssh-client-config.html"><citetitle>&RH;
- Linux 9 Customization Guide</citetitle> </ulink> for details
- about using <command>ssh-agent</command>.
+ Linux 9 Customization Guide</citetitle> </ulink> per i dettagli
+ sull'uso di <command>ssh-agent</command>.
</para>
</tip>
</section>