- Timestamp:
- 05/25/05 16:55:25 (8 years ago)
- Hash name:
- 20050525145525-97f81-6dc0d3af75a6e2a9512ea02e13d3037f657a7e1f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README
r321 r333 267 267 target repository. 268 268 269 269 As another example, consider the following commands:: 270 271 cd /tmp/wc 272 state_file tailor.state 273 source_kind cvs 274 target_kind darcs 275 source_repository :pserver:anonymous@cvs.sourceforge.net:/cvsroot/buildbot 276 source_module buildbot 277 refill_changelogs false 278 patch_name_format %(firstlogline)s 279 print_executed_commands true 280 bootstrap 2004/01/01 20:05:24 281 update ask 282 283 Assuming ``/tmp/wc`` exists, executing them will first bootstrap a new 284 darcs repository with a snapshot at the given date of the upstream 285 sources, then will proceed with the update, asking confirmation about 286 any single changeset:: 287 288 ... 289 Collected 586 upstream changesets 290 Changeset 2004-01-07 00:42:07 by warner: 291 * buildbot/changes/mail.py (parseFreshCVSMail): .... 292 * test/test_mailparse.py (Test1.testMsg9): test for same 293 294 Apply [Y/n/v/h/q]? h 295 y: yes, apply it and keep going 296 n: no, skip the current changeset 297 v: view more detailed information 298 q: do not apply the current changeset and stop iterating 299 300 Apply [Y/n/v/h/q]? v 301 Revision: 2004-01-07 00:42:07 by warner 302 Date: 2004-01-07 00:42:07 303 Author: warner 304 Modified: ChangeLog,buildbot/changes/mail.py,test/test_mailparse.py 305 Added: test/mail/msg9 306 Log: * buildbot/changes/mail.py (parseFreshCVSMail): ... 307 * test/test_mailparse.py (Test1.testMsg9): test for same 308 309 Apply [Y/n/v/h/q]? 310 311 270 312 Further help 271 313 ============
Note: See TracChangeset
for help on using the changeset viewer.
