Re: [fossil-users] Some questions about fossil [importing cvs]
Rene de Zwart wrote: Andreas Kupries wrote: See file c2f_fossil.tcl #!/bin/sh echo fossil $* /your/log/file rc=`__fossil $*` echo $rc /your/log/file echo $rc Right, the result of the command can be of interest too. And the $? variable should hold the exit status of the app after the call. Note. We assumed a basic bourne sh here. If the shell is a bash we can use rc=$(__fossil $*) instead of the backticks. More readable, nestable, better structured. -- Sincerely, Andreas Kupries andr...@activestate.com Developer @http://www.activestate.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Some questions about fossil [importing cvs]
I wonder what the sequence is for importing cvs files into fossil. I tried to get it from cvs2fossil but got lost. first you need to get a commit identifier? assume the following cvs-repository 'example' first.c with rev 1.1 1.2 1.3 1.4 second.c with rev 1.1 1.2 1.3 1.4 and only one user user1 commit 1 first.c rev 1.1 commit 2 first.c rev 1.2 second.c rev 1.1 commit 3 first.c rev 1.3 second.c rev 1.2 commit 4 second.c rev 1.3 commit 5 first.c rev 1.4 second.c 1.4 cvs2fossil does create repository 'example' with user1? then first.c rev 1.1 1.2 1.3 1.4 and then second.c rev 1.1 1.2 1.3 1.4 which test-? are used to accomplish this? Rene On Oct 7, 2009, at 12:01 PM, Ramon Ribó wrote: 1- If someone wants to create a new cvs2fossil, what command can be used to commit a file with an ancient date? Use undocumented flags to commit: --date-override 2009-10-06T12:34:56 --user-override userid 2- How to revert a file to a different version but saving with a different name? You can use the web interface to download any version of any file you want. Your web browser will normally let you choose the name. From the command-line, you can try using the test-content-get command: fossil test-content-get SHA1-hash-of-file output-filename ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users D. Richard Hipp d...@hwaci.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Some questions about fossil [importing cvs]
Rene de Zwart wrote: I wonder what the sequence is for importing cvs files into fossil. I tried to get it from cvs2fossil but got lost. first you need to get a commit identifier? assume the following cvs-repository 'example' first.c with rev 1.1 1.2 1.3 1.4 second.c with rev 1.1 1.2 1.3 1.4 and only one user user1 commit 1 first.c rev 1.1 commit 2 first.c rev 1.2 second.c rev 1.1 commit 3 first.c rev 1.3 second.c rev 1.2 commit 4 second.c rev 1.3 commit 5 first.c rev 1.4 second.c 1.4 cvs2fossil does create repository 'example' with user1? then first.c rev 1.1 1.2 1.3 1.4 and then second.c rev 1.1 1.2 1.3 1.4 which test-? are used to accomplish this? See file c2f_fossil.tcl That contains the code exec'ing fossil. Look for the 'Do ...' calls. cvs2fossil basically imports the files first, by revision, using some test- commands to setup the delta-chain. Then it uses some more test- commands to import the changesets, i.e. sets of file revisions. -- Sincerely, Andreas Kupries andr...@activestate.com Developer @http://www.activestate.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Some questions about fossil [importing cvs]
Andreas Kupries wrote: See file c2f_fossil.tcl That contains the code exec'ing fossil. Look for the 'Do ...' calls. cvs2fossil basically imports the files first, by revision, using some test- commands to setup the delta-chain. Then it uses some more test- commands to import the changesets, i.e. sets of file revisions. Another trick useful in such circumstances: mv fossil __fossil echo eof #!/bin/sh echo fossil $* /your/log/file __fossil $* eof fossil Essentially create a shell script wrapper around the application which logs the invokations and their arguments. -- Sincerely, Andreas Kupries andr...@activestate.com Developer @http://www.activestate.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
