Skip to content

Commit b002cf8

Browse files
committed
[it] translating chapter 6
1 parent 411ed8e commit b002cf8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

it/06-git-tools/01-chapter6.markdown

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -525,13 +525,13 @@ Se accantoni del lavoro e lo lasci lì mentre continui a lavorare per un po' nel
525525
Dropped refs/stash@{0} (f0dfc4d5dc332d1cee34a634182e168c4efc3359)
526526

527527
Questa è una bella accorciatoioa per recuperare il lavoro accantonato e lavorarci in una nuova diramazione.
528-
<!-- da tradurre fino a riga 840 -->
529-
## Rewriting History ##
530528

531-
Many times, when working with Git, you may want to revise your commit history for some reason. One of the great things about Git is that it allows you to make decisions at the last possible moment. You can decide what files go into which commits right before you commit with the staging area, you can decide that you didn’t mean to be working on something yet with the stash command, and you can rewrite commits that already happened so they look like they happened in a different way. This can involve changing the order of the commits, changing messages or modifying files in a commit, squashing together or splitting apart commits, or removing commits entirely — all before you share your work with others.
529+
## Riscrivere la storia ##
532530

533-
In this section, you’ll cover how to accomplish these very useful tasks so that you can make your commit history look the way you want before you share it with others.
531+
Molto spesso, lavorando con Git, you may want to revise your commit history for some reason. One of the great things about Git is that it allows you to make decisions at the last possible moment. You can decide what files go into which commits right before you commit with the staging area, you can decide that you didn’t mean to be working on something yet with the stash command, and you can rewrite commits that already happened so they look like they happened in a different way. This can involve changing the order of the commits, changing messages or modifying files in a commit, squashing together or splitting apart commits, or removing commits entirely — all before you share your work with others.
534532

533+
In this section, you’ll cover how to accomplish these very useful tasks so that you can make your commit history look the way you want before you share it with others.
534+
<!-- da tradurre fino a riga 840 -->
535535
### Changing the Last Commit ###
536536

537537
Changing your last commit is probably the most common rewriting of history that you’ll do. You’ll often want to do two basic things to your last commit: change the commit message, or change the snapshot you just recorded by adding, changing and removing files.

0 commit comments

Comments
 (0)