Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sep:internal:personalbackup [2019/01/29 03:10]
milad
sep:internal:personalbackup [2019/01/29 03:13] (current)
milad
Line 25: Line 25:
          git add myfile1.txt          git add myfile1.txt
  
-  * You can type "git status" to verify that myfile1.txt was added and ready to be committed, whereas myfile2.txt remains untracked. Here myfile1.txt represents files and folders suitable for being backup, such as source codes, makefiles and possibly parameters files. On the contrary, myfile2.txt represents all that you should not incorporate into the backup, such as binaries, results, etc.+  * You can type "git status" to verify that myfile1.txt was added and ready to be committed, whereas myfile2.txt remains untracked. Here myfile1.txt represents files and folders suitable for being backed up, such as source codes, makefiles and possibly parameters files. On the contrary, myfile2.txt represents all that you should not incorporate into the backup, such as binaries, results, etc.
    
 +
 ====  3. Commit your changes==== ====  3. Commit your changes====
   * Once you added the files, you create the local backup using git commit:   * Once you added the files, you create the local backup using git commit:
Line 32: Line 33:
          git commit -m "This is my backup"          git commit -m "This is my backup"
  
-  * Notice that I have added label "-m" which allows to write a message or comment associated to the backup. I strongly recommend you to take advantage of this, for it is easy to lose track of the changes that one makes in one's codes. If you are constantly changing you code, either debugging or testing, it can be wise to commit, for instance, before any "major surgery" that you are palling in your codes, commenting the current status and what you are about to do.+  * Notice that I have added label "-m" which allows to write a message or comment associated to the backup. I strongly recommend you to take advantage of this, for it is easy to lose track of the changes that one makes in one's codes. If you are constantly changing your code, either debugging or testing, it can be wise to commit, for instance, before any "major surgery" that you are palling in your codes, commenting the current status and what you are about to do.
  
 ====  4. Create remote repository (you make this only once)==== ====  4. Create remote repository (you make this only once)====
sep/internal/personalbackup.1548731406.txt.gz ยท Last modified: 2019/01/29 03:10 by milad
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0