Re: [fossil-users] Possible to export revision history?

2010-11-10 Thread Stephan Beal
On Wed, Nov 10, 2010 at 6:09 AM, Gour g...@atmarama.net wrote:

 Excellent!!!

 Thank you very much.


Amen!

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
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] Possible to export revision history?

2010-11-10 Thread J. Cameron Cooper
On Wed, Tue, 9 Nov 2010 20:52:11 -0500, Richard Hipp d...@sqlite.org wrote:

 On Thu, Sep 23, 2010 at 3:15 PM, Todd A. Jacobs 
 codegnome.consulting+fossil-us...@gmail.comcodegnome.consulting%2bfossil-us...@gmail.com
 codegnome.consulting%2bfossil-us...@gmail.comcodegnome.consulting%252bfossil-us...@gmail.com
 
  wrote:

  I'm looking at fossil, and saw a recent post about using git's
  fast-export to get data into fossil. I'm unsure how one gets revision
  history OUT of fossil, though.
 
  If I use fossil, and decide at some point that I want to migrate to
  something else, is there any way to export the revision history of
  artifacts? Something similar to svndump or git's fast-export? Even if
  it isn't *usable* by anything else at the moment, the ability to
  export into some sort of parsable format would be nice.

 The latest checking on trunk (
 http://www.fossil-scm.org/fossil/info/0e87f42762) is able to export all of
 its revision history to Git using the fossil export command.  And it is
 able to import Git revision history using the fossil import command.

 I tested the export capabilities by translating the Fossil and SQLite
 repositories into Git.  And I tested the import function by translating the
 Git repository into Fossil.

 These two new commands (import and export) are early prototypes.  They
 surely still contain bugs and lack needed features.  But I think they
 provide a good start toward an import/export capability for Fossil.

 To convert Fossil into Git:

 git init fdemo
 cd fdemo
 fossil export ~/fossil.fossil | git fast-import

 To convert Git into Fossil:

 git fast-export --signed-tag=strip --tag-of-filtered-object=drop --all
 | fossil import git.fossil

 Please send bug reports, patches, or suggestions for improvement to this
 mailing list, or directly to me.


Just in time to compatible with reposurgeon: http://esr.ibiblio.org/?p=2718

--jcc
-- 
J Cameron Cooper
jccoo...@gmail.com
anyth...@jcameroncooper.com
mobile: 713.882.7395
Skype: jcameroncooper
___
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] Possible to export revision history?

2010-11-09 Thread Richard Hipp
On Thu, Sep 23, 2010 at 3:15 PM, Todd A. Jacobs 
codegnome.consulting+fossil-us...@gmail.comcodegnome.consulting%2bfossil-us...@gmail.com
 wrote:

 I'm looking at fossil, and saw a recent post about using git's
 fast-export to get data into fossil. I'm unsure how one gets revision
 history OUT of fossil, though.

 If I use fossil, and decide at some point that I want to migrate to
 something else, is there any way to export the revision history of
 artifacts? Something similar to svndump or git's fast-export? Even if
 it isn't *usable* by anything else at the moment, the ability to
 export into some sort of parsable format would be nice.



The latest checking on trunk (
http://www.fossil-scm.org/fossil/info/0e87f42762) is able to export all of
its revision history to Git using the fossil export command.  And it is
able to import Git revision history using the fossil import command.

I tested the export capabilities by translating the Fossil and SQLite
repositories into Git.  And I tested the import function by translating the
Git repository into Fossil.

These two new commands (import and export) are early prototypes.  They
surely still contain bugs and lack needed features.  But I think they
provide a good start toward an import/export capability for Fossil.

To convert Fossil into Git:

 git init fdemo
 cd fdemo
 fossil export ~/fossil.fossil | git fast-import

To convert Git into Fossil:

 git fast-export --signed-tag=strip --tag-of-filtered-object=drop --all
| fossil import git.fossil

Please send bug reports, patches, or suggestions for improvement to this
mailing list, or directly to me.
___
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] Possible to export revision history?

2010-11-09 Thread Ron Aaron
On Wednesday 10 November 2010 03:52:11 Richard Hipp wrote:

 
 These two new commands (import and export) are early prototypes.  They
 surely still contain bugs and lack needed features.  But I think they
 provide a good start toward an import/export capability for Fossil.

Excellent!  Any thoughts on making it work with subversion 'dump' format as 
well?

-- 
Sending me something private?
Use my GPG public key: AD29415D


signature.asc
Description: This is a digitally signed message part.
___
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] Possible to export revision history?

2010-11-09 Thread Gour
On Tue, 9 Nov 2010 20:52:11 -0500
 Richard == Richard Hipp wrote:

Richard The latest checking on trunk (
Richard http://www.fossil-scm.org/fossil/info/0e87f42762) is able to
Richard export all of its revision history to Git using the fossil
Richard export command.  And it is able to import Git revision
Richard history using the fossil import command.

Excellent!!! 

Thank you very much.

It's, I believe, very important milestone for Fossil enabling one to
experiment with it without any fear that one is locked-in.


Now I can try to convert one of my old darcs repos to git and import
into Fossil. :-)

Richard These two new commands (import and export) are early
Richard prototypes.  They surely still contain bugs and lack needed
Richard features.  But I think they provide a good start toward an
Richard import/export capability for Fossil.

I'll test and report back if anything is found.

Otoh, few days ago I asked about it on SO, so it would be nice if
someone can send reply there
(http://stackoverflow.com/questions/4119444/is-it-possible-to-export-from-fossil-scm-into-some-other-dvcs)



Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA



signature.asc
Description: PGP signature
___
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] Possible to export revision history?

2010-11-09 Thread Gour
On Wed, 10 Nov 2010 06:47:04 +0200
 Ron == Ron Aaron wrote:

Ron Excellent!  Any thoughts on making it work with subversion 'dump'
Ron format as well?

I don't think it is necessary. There is a tool to convert svn-dump
into git: https://github.com/artagnon/svn-dump-fast-export


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA



signature.asc
Description: PGP signature
___
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] Possible to export revision history?

2010-11-08 Thread Richard Hipp
On Mon, Nov 8, 2010 at 2:04 AM, Gour g...@atmarama.net wrote:


 Considering that all the major DVCS players {bzr,hg,git} as well as
 some like {darcs,monotone} have some kind of tools available to
 convert repo, at least, from X to git, I am also curious how one could
 export history from Fossil?

 It's nice to have git-import converter, but at the same time I believe
 that having some kind of git-export tool would allow more users to try
 going into the Fossil land.


There is a file-format defined for importing and exporting with git.  See

 http://www.kernel.org/pub/software/scm/git/docs/git-fast-import.html

for details.  It appears that if we simply added two commands to Fossil that
would read and write this format, we should be able to import and/or export
Fossil from and to Git.  (Am I correct on that point?)

Are there any volunteers with more git experience than me who are willing to
help with this project?


-- 
D. Richard Hipp
d...@sqlite.org
___
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] Possible to export revision history?

2010-11-08 Thread Gour
On Mon, 8 Nov 2010 08:57:43 -0500
 Richard == Richard Hipp wrote:

Richard It appears that if we simply added two commands to Fossil
Richard that would read and write this format, we should be able to
Richard import and/or export Fossil from and to Git.  (Am I correct
Richard on that point?)

I think so...and it would be great. ;)

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA



signature.asc
Description: PGP signature
___
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] Possible to export revision history?

2010-11-07 Thread Gour
On Thu, 23 Sep 2010 16:30:38 -0400
 Todd == Todd A. Jacobs wrote:

Todd I'm uncomfortable with data silos. I'm freely admitting my
Todd ignorance of fossil internals; I'm just basically asking how
Todd locked in I am if I start a project in fossil and then ever need
Todd to migrate out of it. There's usually a loss of metadata
Todd associated with any import/export, but I'm just trying to
Todd understand what the options are and how much history I could take
Todd with me.

I've the same question...understanding that there is no perfect DVCS
(those which I like as {darcs,monotone} do not have public hosting
solutions, and those which have decent public hosting {bzr,hg} are not
on the top of of my preferences - git/github is excluded), so Fossil
(still) looks as very decent solution to be used for the multi-platform
open-source project - nice DVCS integrating tracker and being easy to
host everything under every shared web hosting.

However, getting in/out of the fossil world is a bit problematic...

Considering that all the major DVCS players {bzr,hg,git} as well as
some like {darcs,monotone} have some kind of tools available to
convert repo, at least, from X to git, I am also curious how one could
export history from Fossil?

It's nice to have git-import converter, but at the same time I believe
that having some kind of git-export tool would allow more users to try
going into the Fossil land.

Any hint?

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA



signature.asc
Description: PGP signature
___
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] Possible to export revision history?

2010-09-27 Thread Wolfgang
Benjamin Pollack benjamin.poll...@... writes:
 Yes. In the move to BSD, Fossil lost both the deconstruct and
 reconstruct commands, since they were GPL-licensed. Someone wrote a
 new BSD-licensed reconstruct, but I don't think anyone's duplicated
 the deconstruct command yet.
 .
 

on branch wolfgangFormat2CSS_2 i recreated the deconstruct command.


___
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] Possible to export revision history?

2010-09-24 Thread Michael Richter
On 24 September 2010 03:20, Richard Hipp d...@sqlite.org wrote:

 The deconstruct method is fossil's equivalent to fast-export.  Why does
 this not meet your needs and what exactly are you looking for?  Are you
 wanting an export in the git-specific format?  How could we export wiki and
 tickets in that case?


What deconstruct method?

mich...@isolde:~$ fossil help

Usage: fossil help COMMAND.

Available COMMANDs:

addco leaves rename ui

allcommit ls revert undo

annotate   configuration  merge  rm unset

artifact   delete mv scrub  update

branch descendantsnewsearch user

cgidiff   open   server version

changesextras pull   settings   wiki

checkout   finfo  push   sha1sumzip

ci gdiff  rebuildstatus

clean  help   reconstructsync

clone  http   redo   tag

close  info   remote-url timeline

This is fossil version [1516a26dc8] 2010-09-16 14:13:51 UTC

mich...@isolde:~$ fossil help deconstruct

fossil: unknown command: deconstruct

mich...@isolde:~$ fossil deconstruct

fossil: unknown command: deconstruct

fossil: use help for more information


I see a reconstruct there, but no matching deconstruct.  Did I do something
bad when building?

-- 
Perhaps people don't believe this, but throughout all of the discussions of
entering China our focus has really been what's best for the Chinese people.
It's not been about our revenue or profit or whatnot.
--Sergey Brin, demonstrating the emptiness of the don't be evil mantra.
___
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] Possible to export revision history?

2010-09-24 Thread Andreas Kupries
On 9/24/2010 10:06 AM, Michael Richter wrote:
 On 24 September 2010 03:20, Richard Hipp d...@sqlite.org
 mailto:d...@sqlite.org wrote:

 The deconstruct method is fossil's equivalent to fast-export.  Why does
 this not meet your needs and what exactly are you looking for?  Are you
 wanting an export in the git-specific format?  How could we export wiki 
 and
 tickets in that case?


 What deconstruct method?


% fossil version
This is fossil version [73c24ae363] 2010-03-18 14:20:33 UTC

% fossil help deconstruct
COMMAND: deconstruct
Usage fossil deconstruct ?-R|--repository REPOSITORY? DESTINATION

Populates the indicated DESTINATION directory with copies of all
artifcats contained within the repository.  Artifacts are named AA/b
where AA is the first 2 characters of the artifact ID and b is the
remaining 38 characters.



 This is fossil version [1516a26dc8] 2010-09-16 14:13:51 UTC

 I see a reconstruct there, but no matching deconstruct.  Did I do something 
 bad
 when building?

Hm. Mine is older than yours. Was this maybe removed in later revisions ?


-- 
Andreas Kupries
Senior Tcl Developer
ActiveState, The Dynamic Language Experts

P: 778.786.1122
F: 778.786.1133
andre...@activestate.com
http://www.activestate.com
Get insights on Open Source and Dynamic Languages at www.activestate.com/blog
___
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] Possible to export revision history?

2010-09-24 Thread Benjamin Pollack
On Fri, Sep 24, 2010 at 1:11 PM, Andreas Kupries
andre...@activestate.com wrote:

 On 9/24/2010 10:06 AM, Michael Richter wrote:
  I see a reconstruct there, but no matching deconstruct.  Did I do something 
  bad
  when building?

 Hm. Mine is older than yours. Was this maybe removed in later revisions ?


Yes. In the move to BSD, Fossil lost both the deconstruct and
reconstruct commands, since they were GPL-licensed. Someone wrote a
new BSD-licensed reconstruct, but I don't think anyone's duplicated
the deconstruct command yet.

--Benjamin
___
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] Possible to export revision history?

2010-09-23 Thread Todd A. Jacobs
On Thu, Sep 23, 2010 at 3:20 PM, Richard Hipp d...@sqlite.org wrote:
 The deconstruct method is fossil's equivalent to fast-export.  Why does
 this not meet your needs and what exactly are you looking for?  Are you
 wanting an export in the git-specific format?  How could we export wiki and
 tickets in that case?

This may be a PEBKAC issue, but when I run deconstruct, I end up with
an unordered tree of hashes. I'm not sure how I would parse any linear
history out of that, even on a per-file (rather than a per-project)
basis.

Since I don't really understand how the wiki and tickets are stored
inside fossil, I don't know why that's a special case. It may very
well be, but I can't address that intelligently.

For example, on GitHub my wiki is just a git repository of text files,
so the wiki is versioned identically to any other object. Ticgit does
something similar with in-repository trouble tickets; they're just
versioned text files in a special git branch.

I'm uncomfortable with data silos. I'm freely admitting my ignorance
of fossil internals; I'm just basically asking how locked in I am if I
start a project in fossil and then ever need to migrate out of it.
There's usually a loss of metadata associated with any import/export,
but I'm just trying to understand what the options are and how much
history I could take with me.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users