141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
-
+
-
+
-
+
+
+
+
+
-
+
|
David also suggested allowing open's argument to be a URL, in which case it would clone the repository, make a directory for it, and open into the directory. It's not clear what the local repository filename would be, where to store it, and where to open it. A convention could be established to handle these things.
------
*On 2015-03-07 19:12:15 UTC andygoth added:*
# Merge /dir and /tree
# Merge /dir and /tree.
It's unclear why these are separate. I advocate merging the code. Whichever one gets axed could be made to redirect to the other.
------
*On 2015-05-15 05:49:01 UTC andygoth added:*
# Merge update and checkout
# Merge update and checkout. <i>(Withdrawn)</i>
The checkout command is very nearly the same as update. The only differences I can think of are that checkout doesn't trigger an autosync, plus it has -keep to change which checkout is selected without actually modifying files. (Also it has -force, but that's to work around a limitation of checkout not present in update.) <i>-- drh replies:
The checkout command is very nearly the same as update. The only differences I can think of are that checkout doesn't trigger an autosync, plus it has -keep to change which checkout is selected without actually modifying files. (Also it has -force, but that's to work around a limitation of checkout not present in update.)
I actually use "checkout -force -keep" a bunch when synchronizing Fossil with other revision control systems, so this functionality must remain, even if it becomes "update -keep".
<i>-- drh replies:
Update merges any changes in the working directory over to the new version.
Checkout does not. Checkout requires that there be no changes in the working
directory, or else that the --force flag be used which overwrites all local
changes.</i>
I actually use "checkout -force -keep" a bunch when synchronizing Fossil with other revision control systems, so this functionality must remain, even if it becomes "update -keep".
If there is a well-defined difference between update and checkout, I am fine with them being separate. Prior to your explanation, they seemed so similar it was arbitrary that they be kept separate. Checkout selects exactly a particular checkout.
|