Fossil SCM
Added missing commit example to 5-minute quickstart.
Commit
0fb6c829f2dbf6580315c05eb6c854065d1b9267
Parent
be93ecb3a5758b8…
1 file changed
+14
+14
| --- www/fiveminutes.wiki | ||
| +++ www/fiveminutes.wiki | ||
| @@ -7,44 +7,56 @@ | ||
| 7 | 7 | |
| 8 | 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | 10 | user, ie. with no additional users, with no need to synchronize with some remote |
| 11 | 11 | repository, and no need for branching/forking.</p> |
| 12 | + | |
| 12 | 13 | <h2>Create a new repository</h2> |
| 13 | 14 | <p>fossil new c:\test.repo</p> |
| 14 | 15 | <p>This will create the new SQLite binary file that holds the repository, ie. |
| 15 | 16 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 16 | 17 | best practise to keep it outside the work directory where you will work on files |
| 17 | 18 | after they've been checked out of the repository.</p> |
| 19 | + | |
| 18 | 20 | <h2>Open the repository</h2> |
| 19 | 21 | <p>cd c:\temp\test.fossil</p> |
| 20 | 22 | <p>fossil open c:\test.repo</p> |
| 21 | 23 | <p>This will check out the last revision of all the files in the repository, |
| 22 | 24 | if any, into the current work directory. In addition, it will create a binary |
| 23 | 25 | file _FOSSIL_ to keep track of changes (on non-Windows systems it is called |
| 24 | 26 | <tt>.fslckout</tt>).</p> |
| 27 | + | |
| 25 | 28 | <h2>Add new files</h2> |
| 26 | 29 | <p>fossil add .</p> |
| 27 | 30 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 28 | 31 | added until you run "commit". When using ".", it tells Fossil |
| 29 | 32 | to add all the files in the current directory recursively, ie. including all |
| 30 | 33 | the files in all the subdirectories.</p> |
| 31 | 34 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 32 | 35 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 36 | + | |
| 33 | 37 | <h2>Remove files that haven't been commited yet</h2> |
| 34 | 38 | <p>fossil delete myfile.c</p> |
| 35 | 39 | <p>This will simply remove the item from the list of files that were previously |
| 36 | 40 | added through "fossil add".</p> |
| 41 | + | |
| 37 | 42 | <h2>Check current status</h2> |
| 38 | 43 | <p>fossil changes</p> |
| 39 | 44 | <p>This shows the list of changes that have been done and will be commited the |
| 40 | 45 | next time you run "fossil commit". It's a useful command to run before |
| 41 | 46 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 47 | + | |
| 42 | 48 | <h2>Commit changes</h2> |
| 43 | 49 | <p>To actually apply the pending changes to the repository, eg. new files marked |
| 44 | 50 | for addition, checked-out files that have been edited and must be checked-in, |
| 45 | 51 | etc.</p> |
| 52 | + | |
| 53 | +<p>fossil commit -m "Added stuff"</p> | |
| 54 | + | |
| 55 | +If no file names are provided on the command-line then all changes will be checked in, | |
| 56 | +otherwise just the listed file(s) will be checked in. | |
| 57 | + | |
| 46 | 58 | <h2>Compare two revisions of a file</h2> |
| 47 | 59 | <p>If you wish to compare the last revision of a file and its checked out version |
| 48 | 60 | in your work directory:</p> |
| 49 | 61 | <p>fossil gdiff myfile.c</p> |
| 50 | 62 | <p>If you wish to compare two different revisions of a file in the repository:</p> |
| @@ -53,10 +65,12 @@ | ||
| 53 | 65 | <p>fossil gdiff --from UUID#1 --to UUID#2 myfile.c</p> |
| 54 | 66 | <h2>Cancel changes and go back to previous revision</h2> |
| 55 | 67 | <p>fossil revert myfile.c</p> |
| 56 | 68 | <p>Fossil does not prompt when reverting a file. It simply reminds the user about the |
| 57 | 69 | "undo" command, just in case the revert was a mistake.</p> |
| 70 | + | |
| 71 | + | |
| 58 | 72 | <h2>Close the repository</h2> |
| 59 | 73 | <p>fossil close</p> |
| 60 | 74 | <p>This will simply remote the _FOSSIL_ at the root of the work directory but |
| 61 | 75 | will not delete the files in the work directory. From then on, any use of "fossil" |
| 62 | 76 | will trigger an error since there is no longer any connection.</p> |
| 63 | 77 |
| --- www/fiveminutes.wiki | |
| +++ www/fiveminutes.wiki | |
| @@ -7,44 +7,56 @@ | |
| 7 | |
| 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | user, ie. with no additional users, with no need to synchronize with some remote |
| 11 | repository, and no need for branching/forking.</p> |
| 12 | <h2>Create a new repository</h2> |
| 13 | <p>fossil new c:\test.repo</p> |
| 14 | <p>This will create the new SQLite binary file that holds the repository, ie. |
| 15 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 16 | best practise to keep it outside the work directory where you will work on files |
| 17 | after they've been checked out of the repository.</p> |
| 18 | <h2>Open the repository</h2> |
| 19 | <p>cd c:\temp\test.fossil</p> |
| 20 | <p>fossil open c:\test.repo</p> |
| 21 | <p>This will check out the last revision of all the files in the repository, |
| 22 | if any, into the current work directory. In addition, it will create a binary |
| 23 | file _FOSSIL_ to keep track of changes (on non-Windows systems it is called |
| 24 | <tt>.fslckout</tt>).</p> |
| 25 | <h2>Add new files</h2> |
| 26 | <p>fossil add .</p> |
| 27 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 28 | added until you run "commit". When using ".", it tells Fossil |
| 29 | to add all the files in the current directory recursively, ie. including all |
| 30 | the files in all the subdirectories.</p> |
| 31 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 32 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 33 | <h2>Remove files that haven't been commited yet</h2> |
| 34 | <p>fossil delete myfile.c</p> |
| 35 | <p>This will simply remove the item from the list of files that were previously |
| 36 | added through "fossil add".</p> |
| 37 | <h2>Check current status</h2> |
| 38 | <p>fossil changes</p> |
| 39 | <p>This shows the list of changes that have been done and will be commited the |
| 40 | next time you run "fossil commit". It's a useful command to run before |
| 41 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 42 | <h2>Commit changes</h2> |
| 43 | <p>To actually apply the pending changes to the repository, eg. new files marked |
| 44 | for addition, checked-out files that have been edited and must be checked-in, |
| 45 | etc.</p> |
| 46 | <h2>Compare two revisions of a file</h2> |
| 47 | <p>If you wish to compare the last revision of a file and its checked out version |
| 48 | in your work directory:</p> |
| 49 | <p>fossil gdiff myfile.c</p> |
| 50 | <p>If you wish to compare two different revisions of a file in the repository:</p> |
| @@ -53,10 +65,12 @@ | |
| 53 | <p>fossil gdiff --from UUID#1 --to UUID#2 myfile.c</p> |
| 54 | <h2>Cancel changes and go back to previous revision</h2> |
| 55 | <p>fossil revert myfile.c</p> |
| 56 | <p>Fossil does not prompt when reverting a file. It simply reminds the user about the |
| 57 | "undo" command, just in case the revert was a mistake.</p> |
| 58 | <h2>Close the repository</h2> |
| 59 | <p>fossil close</p> |
| 60 | <p>This will simply remote the _FOSSIL_ at the root of the work directory but |
| 61 | will not delete the files in the work directory. From then on, any use of "fossil" |
| 62 | will trigger an error since there is no longer any connection.</p> |
| 63 |
| --- www/fiveminutes.wiki | |
| +++ www/fiveminutes.wiki | |
| @@ -7,44 +7,56 @@ | |
| 7 | |
| 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | user, ie. with no additional users, with no need to synchronize with some remote |
| 11 | repository, and no need for branching/forking.</p> |
| 12 | |
| 13 | <h2>Create a new repository</h2> |
| 14 | <p>fossil new c:\test.repo</p> |
| 15 | <p>This will create the new SQLite binary file that holds the repository, ie. |
| 16 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 17 | best practise to keep it outside the work directory where you will work on files |
| 18 | after they've been checked out of the repository.</p> |
| 19 | |
| 20 | <h2>Open the repository</h2> |
| 21 | <p>cd c:\temp\test.fossil</p> |
| 22 | <p>fossil open c:\test.repo</p> |
| 23 | <p>This will check out the last revision of all the files in the repository, |
| 24 | if any, into the current work directory. In addition, it will create a binary |
| 25 | file _FOSSIL_ to keep track of changes (on non-Windows systems it is called |
| 26 | <tt>.fslckout</tt>).</p> |
| 27 | |
| 28 | <h2>Add new files</h2> |
| 29 | <p>fossil add .</p> |
| 30 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 31 | added until you run "commit". When using ".", it tells Fossil |
| 32 | to add all the files in the current directory recursively, ie. including all |
| 33 | the files in all the subdirectories.</p> |
| 34 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 35 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 36 | |
| 37 | <h2>Remove files that haven't been commited yet</h2> |
| 38 | <p>fossil delete myfile.c</p> |
| 39 | <p>This will simply remove the item from the list of files that were previously |
| 40 | added through "fossil add".</p> |
| 41 | |
| 42 | <h2>Check current status</h2> |
| 43 | <p>fossil changes</p> |
| 44 | <p>This shows the list of changes that have been done and will be commited the |
| 45 | next time you run "fossil commit". It's a useful command to run before |
| 46 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 47 | |
| 48 | <h2>Commit changes</h2> |
| 49 | <p>To actually apply the pending changes to the repository, eg. new files marked |
| 50 | for addition, checked-out files that have been edited and must be checked-in, |
| 51 | etc.</p> |
| 52 | |
| 53 | <p>fossil commit -m "Added stuff"</p> |
| 54 | |
| 55 | If no file names are provided on the command-line then all changes will be checked in, |
| 56 | otherwise just the listed file(s) will be checked in. |
| 57 | |
| 58 | <h2>Compare two revisions of a file</h2> |
| 59 | <p>If you wish to compare the last revision of a file and its checked out version |
| 60 | in your work directory:</p> |
| 61 | <p>fossil gdiff myfile.c</p> |
| 62 | <p>If you wish to compare two different revisions of a file in the repository:</p> |
| @@ -53,10 +65,12 @@ | |
| 65 | <p>fossil gdiff --from UUID#1 --to UUID#2 myfile.c</p> |
| 66 | <h2>Cancel changes and go back to previous revision</h2> |
| 67 | <p>fossil revert myfile.c</p> |
| 68 | <p>Fossil does not prompt when reverting a file. It simply reminds the user about the |
| 69 | "undo" command, just in case the revert was a mistake.</p> |
| 70 | |
| 71 | |
| 72 | <h2>Close the repository</h2> |
| 73 | <p>fossil close</p> |
| 74 | <p>This will simply remote the _FOSSIL_ at the root of the work directory but |
| 75 | will not delete the files in the work directory. From then on, any use of "fossil" |
| 76 | will trigger an error since there is no longer any connection.</p> |
| 77 |