Dear list members,
We are currently using cvs to maintain many different projects in
our company. After reviewing fossil, it looks as a very nice piece of
software that can make a much better job than cvs for our development
needs. So, we are considering the possibility of moving into fossil
1- If someone wants to create a new cvs2fossil, what command can be
used to commit a
file with an ancient date?
2- How to revert a file to a different version but saving with a
different name?
___
fossil-users mailing list
fossil-users@lists.fossil
On Oct 4, 2009, at 6:42 AM, Ramon Ribó wrote:
>
> 2- Why is it not possible to start a new fossil directory inside a
> subdirectory of another fossil directory? This is a structure that we
>use very often with cvs. I do not see the technical difficulties
> for this. Just when descending or asc
Thanks for the answers. More comments:
> Why not just check out the whole thing? What is the point of checking
> out a partial tree? Are you really that short of disk space?
Of course, this is not a disk space issue. There are several reasons to
consider it as an advantage:
- Some packages are
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
D. Richard Hipp wrote:
> 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-ov
> Oh. I didn't know about these (while writing cvs2fossil). Which is why I put
> this information into the new commit message. Since when do they exist ?
Andreas, I see that you are the developer of cvs2fossil. I have tried it and I
have had some problems with it (the details are in another mess
Ramon Ribó wrote:
>> Oh. I didn't know about these (while writing cvs2fossil). Which is why I put
>> this information into the new commit message. Since when do they exist ?
>
> Andreas, I see that you are the developer of cvs2fossil. I have tried it
> and I
> have had some problems with it (th
Andreas,
The problems were:
1- I have been trying to use the tool cvs2fossil with a simple, few
files, no branches, small cvs project. For testing. Results:
a) changed tag branch ---> branch new in file c2f_fossil.tcl (this
error has been discussed in the list but is not corrected in the
Andreas Kupries wrote:
> Ramon Ribó wrote:
> What about the third option ? I.e. editing cvs2fossil instead of developing
> from scratch ?
Another option: write fossil support for tailor -
http://progetti.arstecnica.it/tailor - which would give migration
support to a large number of other VCS / D
While I realize that this is a somewhat different emphasis than fossil's
usual orientation, I have suggested to my work superiors that fossil may
be usable for us as a document repository, given its (lack of) cost and
its additional features we could leverage. Almost exclusively, the
documents we
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
co
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
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
> im
> 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- command
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 $? vari
> 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.
> An
Rene de Zwart wrote:
> there is one slight problem ;-)
>
> fossil get feed with
> fossil test-import-manifest 1255003794 By renez: example repostory -f
> 2 example/first
>
> instead of
> fossil test-import-manifest 1255003794 "By renez: example repostory"
> -f 2 example/first
Ok. This ma
On Tue, 15 Jan 2013 16:37:46 -0600
Carson Chittom wrote:
> While I realize that this is a somewhat different emphasis than
> fossil's usual orientation, I have suggested to my work superiors
> that fossil may be usable for us as a document repository, given its
> (lack of) cost and its additional
"C. Thomas Stover" writes:
> On Tue, 15 Jan 2013 16:37:46 -0600
> Carson Chittom wrote:
>
>> While I realize that this is a somewhat different emphasis than
>> fossil's usual orientation, I have suggested to my work superiors
>> that fossil may be usable for us as a document repository, given it
On Wed, 16 Jan 2013 16:11:49 -0600
Carson Chittom wrote:
> Yes, basically, it's the "probably should save for later" need--mostly
> for legal reasons. Currently all this is in hardcopy, as I mentioned,
> the volume of which has reached such a level as to be simply
> impenetrable; part of the rea
t
while viewing the original scanned copy. I do this for bills and such at home.
I personally don't see fossil as the right tool for a document repo.
Tomek
> Date: Wed, 16 Jan 2013 16:33:09 -0600
> From: c...@thomasstover.com
> To: fossil-users@lists.fossil-scm.org
> Subject: Re
C. Thomas Stover wrote:
> On the other hand, if you are trying to do actual collaborative work on
> documents, then it is absolutely critical that in addition to a SCM
> system (fossil would be great), that you move to a text/source based
> document generation technology.
The real problem is a la
Tomek Kott writes:
> Might I suggest the following two tools as better suited for this sort
> of endeavor?
>
> 1) Zotero - http://www.zotero.org/
This looks very interesting, and I can see where I might find a use for
it myself in my personal life. Unfortunately, I don't think it will be
a sol
"C. Thomas Stover" writes:
> Well if hardcopy means scanned paper (no ocr) then it sounds like a
> very large binary file set.
I'm showing my ignorance, but does OCR matter in this case? We already
have OCR capabilities, and I had intended to scan in the documents using
it--because, why not, i
On Thu, 17 Jan 2013 07:55:09 -0600
Carson Chittom wrote:
> "C. Thomas Stover" writes:
>
> > Well if hardcopy means scanned paper (no ocr) then it sounds like a
> > very large binary file set.
>
> I'm showing my ignorance, but does OCR matter in this case? We
> already have OCR capabilities,
On Thu, Jan 17, 2013 at 6:53 PM, C. Thomas Stover wrote:
> both images and text can be stored, the scanner software/firmware will
> OCR what it can and then mix that with little cropped images. This of
> course leads to the "your mileage may very" file sizes.
>
FWIW: if the documents are having t
On Thu, 17 Jan 2013 18:53:43 +0100, C. Thomas Stover
wrote:
On Thu, 17 Jan 2013 07:55:09 -0600
Carson Chittom wrote:
"C. Thomas Stover" writes:
> Well if hardcopy means scanned paper (no ocr) then it sounds like a
> very large binary file set.
I'm showing my ignorance, but does OCR matt
On Thu, 17 Jan 2013 19:48:20 +0100
Stephan Beal wrote:
> FWIW: if the documents are having to be archived "for legal reasons"
> then the OCR versions are essentially only useful for convenience in
> searching, and not for legal purposes.
that's good information to know
On Thu, 17 Jan 2013 19:51
Stephan Beal writes:
> On Thu, Jan 17, 2013 at 6:53 PM, C. Thomas Stover
> wrote:
>
>> both images and text can be stored, the scanner software/firmware will
>> OCR what it can and then mix that with little cropped images. This of
>> course leads to the "your mileage may very" file sizes.
>>
>
>
ave found it an indispensable tool for managing and finding
information.
--
Regards,
David Baxendale
Message: 5
Date: Wed, 16 Jan 2013 19:31:59 -0500
From: Tomek Kott
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] some questions about
fossil-as-document-repo
Mess
On 01/17/2013 02:29 PM, Carson Chittom wrote:
But these are not "legal" documents in the sense I
think you mean--contracts, etc. Our lawyer keeps those. Our use case is more
of a question of one of our staff being able to find something that
documents that previously we did x in case y, so if w
On Fri, Jan 18, 2013 at 09:33:05AM +0800, David Baxendale (GMail - Singapore)
wrote:
> I don't think Fossil is the right tool for this, take a look at Calibre
> (http://calibre-ebook.com/) as an Open Source document management
> system, not just an e-book reader.
Calibre can't handle severa
33 matches
Mail list logo
