Re: [fossil-users] importing/forking from Git
On Mon, Mar 10, 2014 at 06:31:25PM -0400, Ron Wilson wrote: On Sat, Mar 8, 2014 at 5:17 PM, Chad Perrin c...@apotheon.net wrote: Should I take it at this point that --incremental is deprecated and should not be used or expected to be present in future Fossil versions? So far, I have seen no responses that specifically addressed whether the behavior I expected from it was the intended behavior, whether anyone else might have the same problem indicating a bug in the software or whether this was confined to my situation and thus might be a local configuration issue, whether there was anything I could do to provide more information to help, and so on. The closest thing to meaningfully addressing the issue that I have seen was akin to the old joke . . . patient: Doctor, doctor, it hurts when I do this! doctor: Don't do that. I very much doubt that --incremental would be deprecated. I suspect that no one else has tried your use case. I'm stuck in kind of a no-win situation with this, then. It's not really appropriate to log a bug in an issue tracker without knowing it's a bug, but nobody will tell me if it's a bug, how I should judge whether it's a bug, or whatever else applies here. I'm not even sure yet that what I believe to be expected behavior is expected behavior, or whether I'm just using it wrong. . . . so while I wait to see if someone will give me some guidance, it will fall off everyone's radar, and nothing will be done, so that my only option going forward for some of these projects will be to just use Git. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Wed, Mar 12, 2014 at 5:04 PM, Chad Perrin c...@apotheon.net wrote: I'm stuck in kind of a no-win situation with this, then. It's not really appropriate to log a bug in an issue tracker without knowing it's a bug, but nobody will tell me if it's a bug, how I should judge whether it's a bug, or whatever else applies here. I'm not even sure yet that what I believe to be expected behavior is expected behavior, or whether I'm just using it wrong. You could put in an enhancement request. What you want to do, import in to a repository with only the initial, empty commit, seems reasonable. . . . so while I wait to see if someone will give me some guidance, it will fall off everyone's radar, and nothing will be done, so that my only option going forward for some of these projects will be to just use Git. If the only possible way to start a new repository on the server is fossil new repoName.fossil, then a possible work around would be to do a normal import to Fossil, then create a marks file (see fossil help export) with the RID of the initial, empty commit, then use the --import-marks option to the fossil export command to (hopefully) create something usable with fossil import --incremental. Not sure when I will be able to experiemnt with this more. ___ 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] importing/forking from Git
On Sat, Mar 8, 2014 at 5:17 PM, Chad Perrin c...@apotheon.net wrote: Should I take it at this point that --incremental is deprecated and should not be used or expected to be present in future Fossil versions? So far, I have seen no responses that specifically addressed whether the behavior I expected from it was the intended behavior, whether anyone else might have the same problem indicating a bug in the software or whether this was confined to my situation and thus might be a local configuration issue, whether there was anything I could do to provide more information to help, and so on. The closest thing to meaningfully addressing the issue that I have seen was akin to the old joke . . . patient: Doctor, doctor, it hurts when I do this! doctor: Don't do that. I very much doubt that --incremental would be deprecated. I suspect that no one else has tried your use case. I still haven't been able to experiment more, but it occurs to me that fossil import --incremental would assume that its input resulted from git --fast-export --incremental. Further, I would expect the --incremental option to git to require that an initial non-incremental export had already been done. From reading about Fossil export, it seems there might be a way to fake an initial non-incremental export from Fossil. If that is so (or if this can be done directly in git), then I would expect fossil import --incremental to work as you want. Of course, it would be useful for Fossil to support non-incremental import to an existing repository, at least one with only the initial, empty commit. ___ 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] importing/forking from Git
Should I take it at this point that --incremental is deprecated and should not be used or expected to be present in future Fossil versions? So far, I have seen no responses that specifically addressed whether the behavior I expected from it was the intended behavior, whether anyone else might have the same problem indicating a bug in the software or whether this was confined to my situation and thus might be a local configuration issue, whether there was anything I could do to provide more information to help, and so on. The closest thing to meaningfully addressing the issue that I have seen was akin to the old joke . . . patient: Doctor, doctor, it hurts when I do this! doctor: Don't do that. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Wed, Mar 5, 2014 at 2:21 AM, Chad Perrin c...@apotheon.net wrote: I'm talking about a distributed team, where not everyone has SSH shell access or the ability to directly change anything on the filesystem, but they all have commit access to a specific set of repositories. This means, for instance, that they could clone from, and sync with, an existing repository -- but not all could create or delete entire repositories. Presumably the server admin (you?) would be the one creating new repositories on the server, so would be able to use fossil clone or fossil import either via SSH or directly on the server. I tried experimenting with the --incremental option. It appears to work for keeping a Fossil repository up to date after the initial import. I don't know if that is an intended limitation or a bug. Right now, I don't have more time to experiment with it as it is not a feature I use. ___ 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] importing/forking from Git
On Wed, Mar 05, 2014 at 07:25:31PM -0500, Ron Wilson wrote: On Wed, Mar 5, 2014 at 2:21 AM, Chad Perrin c...@apotheon.net wrote: I'm talking about a distributed team, where not everyone has SSH shell access or the ability to directly change anything on the filesystem, but they all have commit access to a specific set of repositories. This means, for instance, that they could clone from, and sync with, an existing repository -- but not all could create or delete entire repositories. Presumably the server admin (you?) would be the one creating new repositories on the server, so would be able to use fossil clone or fossil import either via SSH or directly on the server. As I said in another response within this extended thread: . . . there may be a fair number of similar import/fork needs in the future, which means that it makes a lot more sense for me to figure out how to get the import into an existing repository to work -- especially because people who do not have scp access to the server at the moment may also be doing some of this work. If I just do it the way you describe, I would need to do all of this work for every instance, which is not a very reasonable state of affairs here. The result is that, yes, if it was *just me*, and/or I was willing to *do everything all the time*, it would be possible for me to do things in a *more difficult way* every time, but I'm not likely to do any of: 1. give everyone in the world the ability to make these changes on the server directly 2. screw around endlessly with ssh key configuration to limit privileges to a particular set of commands that will probably end up changing regularly so that I have to do that again, then again, and so on 3. do a bunch of extra work on top of extra work other people need to do -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil The above should be all you need to do. It should just work. And it does just work for every git repository that I've tried, though that is, admittedly, not that many repos. If you are willing to share with us the specific repo you are trying to import, prehaps the developers can try it and discover what's going wrong. No files appear. I looked at the timeline: $ fossil timeline === 2014-03-04 === 20:24:06 [178338650a] *CURRENT* initial empty check-in (user: apotheon tags: trunk) === 2013-06-19 === 21:12:33 [34ca661224] last commit message from Git === 2011-10-16 === . . . et cetera The obvious choice seems to be to use revert: $ fossil help revert Usage: fossil revert ?-r REVISION? ?FILE ...? Revert to the current repository version of FILE, or to the version associated with baseline REVISION if the -r flag appears. [. . .] Revert all files if no file name is provided. [. . .] I tried that: $ fossil revert -r 34ca661224 the --revision option does not work for the entire tree How do I actually get a repository import to a usable state so I can push it to the server's repository and get on with my life? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ 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...@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] importing/forking from Git
On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil Doesn't the git import create the fossil repo for you? Maybe you should try doing the import into a fossil repo that doesn't already exist. Then you can scp that repo to your server and clone it down. I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil The above should be all you need to do. It should just work. And it does just work for every git repository that I've tried, though that is, admittedly, not that many repos. If you are willing to share with us the specific repo you are trying to import, prehaps the developers can try it and discover what's going wrong. No files appear. I looked at the timeline: $ fossil timeline === 2014-03-04 === 20:24:06 [178338650a] *CURRENT* initial empty check-in (user: apotheon tags: trunk) === 2013-06-19 === 21:12:33 [34ca661224] last commit message from Git === 2011-10-16 === . . . et cetera The obvious choice seems to be to use revert: $ fossil help revert Usage: fossil revert ?-r REVISION? ?FILE ...? Revert to the current repository version of FILE, or to the version associated with baseline REVISION if the -r flag appears. [. . .] Revert all files if no file name is provided. [. . .] I tried that: $ fossil revert -r 34ca661224 the --revision option does not work for the entire tree How do I actually get a repository import to a usable state so I can push it to the server's repository and get on with my life? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ 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...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- James Turner ___ 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] importing/forking from Git
On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil The above should be all you need to do. It should just work. And it does just work for every git repository that I've tried, though that is, admittedly, not that many repos. If you are willing to share with us the specific repo you are trying to import, prehaps the developers can try it and discover what's going wrong. git://repo.or.cz/nvi.git For reference, I'm using . . . $ fossil version This is fossil version 1.28 [3d49f04587] 2014-01-27 17:33:44 UTC . . . on FreeBSD, installed from ports, with the JSON and STATIC options both selected at build time. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
I did this: mkdir nvi cd nvi git clone git://repo.or.cz/nvi.git cd nvi git fast-export --all | fossil import ../nvi.fossil cd .. mkdir n2 cd n2 fossil open ../nvi.fossil The result was a directory full of files. And I could do fossil ui to see the complete development timeline, and so forth. On Tue, Mar 4, 2014 at 3:55 PM, Chad Perrin c...@apotheon.net wrote: On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil The above should be all you need to do. It should just work. And it does just work for every git repository that I've tried, though that is, admittedly, not that many repos. If you are willing to share with us the specific repo you are trying to import, prehaps the developers can try it and discover what's going wrong. git://repo.or.cz/nvi.git For reference, I'm using . . . $ fossil version This is fossil version 1.28 [3d49f04587] 2014-01-27 17:33:44 UTC . . . on FreeBSD, installed from ports, with the JSON and STATIC options both selected at build time. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ 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...@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] importing/forking from Git
On Tue, Mar 04, 2014 at 01:55:36PM -0700, Chad Perrin wrote: On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil Bah incremental requires the repo to exist. Without incremental the import is successful and trunk is set correctly. I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil The above should be all you need to do. It should just work. And it does just work for every git repository that I've tried, though that is, admittedly, not that many repos. If you are willing to share with us the specific repo you are trying to import, prehaps the developers can try it and discover what's going wrong. git://repo.or.cz/nvi.git For reference, I'm using . . . $ fossil version This is fossil version 1.28 [3d49f04587] 2014-01-27 17:33:44 UTC . . . on FreeBSD, installed from ports, with the JSON and STATIC options both selected at build time. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- James Turner ___ 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] importing/forking from Git
On Tue, Mar 4, 2014 at 4:02 PM, James Turner ja...@calminferno.net wrote: Bah incremental requires the repo to exist. Without incremental the import is successful and trunk is set correctly. I completely overlooked the --incremental flag in the original post. Sorry... -- 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] importing/forking from Git
On Tue, Mar 04, 2014 at 04:01:36PM -0500, Richard Hipp wrote: I did this: mkdir nvi cd nvi git clone git://repo.or.cz/nvi.git cd nvi git fast-export --all | fossil import ../nvi.fossil cd .. mkdir n2 cd n2 fossil open ../nvi.fossil The result was a directory full of files. And I could do fossil ui to see the complete development timeline, and so forth. My understanding is that --incremental, as used in my original attempt described in my email to start this thread, should allow me to import into an existing Fossil repository. That is where I am having a problem. Do I misunderstand the intended use of --incremental? Is there some way to let someone push from a fresh Fossil repository created by import from git to an existing repository on another server, which I could use instead? The key here is that someone without the ability to brute-force copy (i.e. scp) the projectname.fossil file to the server should be able to import from git then use the fossil utility to push that to a repository on the server, resulting in a repository full of files and history. Is that possible, or do I pretty much need to either throw away all history or just stick with Git instead? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
The following is based on the fact that I do not know whether there are any undocumented or poorly-documented features that would provide the described functionality, or whether I have simply failed to see what was right in front of my face after spending a fair bit of time staring at Fossil's help output. ## Related Questions Is there some way to merge history from another fossil repository into a brand new fossil repository created with fossil init locally? This would help me by allowing me to clone the repository from the server and import from Git to create a new repository, then merge from that new repository into the repository cloned from the server, then push changes to the repository on the server. Is there some way to push from a fossil repository to an arbitrary brand-new repository across HTTP(S)? This would help me by allowing me to import from Git to create a new repository, then simply push from the new Fossil repository to the existing (empty) repository on the server. The ability to do this seems like it would have many, many other potential uses in truly distributed version control workflows, too -- even if it only pushed (with all history) as a branch. Is there some way to create a repository so it does not have a dated initial commit just because the init command was used? It seems odd to me that the only DVCS that I have seen that cannot init a repository without an implicit initial commit is Fossil, and this would likely solve my present problem as well. Is there some way to revert the state of an entire repository, involving all files, to an earlier state? It never occurred to me there may not be, and this was obviously part of my earlier attempt to make the import work out for my needs. It seems that the ability to roll back the entire repository to an earlier state should exist for a variety of reasons, perhaps relegating anything undone by the rollback to a dead/closed branch. ## Unrelated Questions Is there any chance that Fossil will get a manpage or two at some point? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Tue, Mar 4, 2014 at 10:58 PM, Chad Perrin c...@apotheon.net wrote: Is there any chance that Fossil will get a manpage or two at some point? Perhaps this suffices (or provides a start): http://fossil-scm.org/index.html/help The /help page can also be accessed locally via (fossil ui). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] importing/forking from Git
On Tue, Mar 04, 2014 at 03:49:26PM -0500, James Turner wrote: On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil Doesn't the git import create the fossil repo for you? Maybe you should try doing the import into a fossil repo that doesn't already exist. According to the fossil help import documentation, --incremental should work with an existing Fossil repository rather than creating a new one. Then you can scp that repo to your server and clone it down. This is an operation that would be much more convenient to accomplish the way I've already tried to do it, in current circumstances, and there may be a fair number of similar import/fork needs in the future, which means that it makes a lot more sense for me to figure out how to get the import into an existing repository to work -- especially because people who do not have scp access to the server at the moment may also be doing some of this work. If I just do it the way you describe, I would need to do all of this work for every instance, which is not a very reasonable state of affairs here. In any case, I would much rather (help) fix a problem, or learn how to do it right if the error is mine rather than the software's, than just sweep the problem under the rug and use a work-around. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Tue, Mar 04, 2014 at 11:16:07PM +0100, Stephan Beal wrote: On Tue, Mar 4, 2014 at 10:58 PM, Chad Perrin c...@apotheon.net wrote: Is there any chance that Fossil will get a manpage or two at some point? Perhaps this suffices (or provides a start): http://fossil-scm.org/index.html/help The /help page can also be accessed locally via (fossil ui). I'm aware of the web help. I'm just wondering about whether it'll ever get a manpage. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil Is there some reason you can't do fossil clone on the server? Alternately, try: $ git fast-export --all |ssh user@server fossil import\ --git --incremental /path/to/projectname.fossil I imported from Git: $ git fast-export --all | fossil import --git --incremental \ /path/to/projectname.fossil I opened the repository: $ mkdir projectname; cd projectname fossil open /path/to/projectname.fossil No files appear. I looked at the timeline: That is surprising to me. Though I have not used this feature. ___ 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] importing/forking from Git
On Tue, Mar 4, 2014 at 7:12 PM, Ron Wilson ronw.m...@gmail.com wrote: Alternately, try: $ git fast-export --all |ssh user@server fossil import\ --git --incremental /path/to/projectname.fossil Oops. Don't use the --incremental for the initial import. ___ 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] importing/forking from Git
On Tue, Mar 04, 2014 at 07:12:54PM -0500, Ron Wilson wrote: On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin c...@apotheon.net wrote: Trying to fork/import from Git is kinda problematic. I started by creating a new project on a server: $ fossil init projectname.fossil I then cloned locally: $ fossil clone u...@uri.for/projectname/index.cgi projectname.fossil Is there some reason you can't do fossil clone on the server? Alternately, try: $ git fast-export --all |ssh user@server fossil import\ --git --incremental /path/to/projectname.fossil Both of those solutions would surely work in this case (as long as the incremental option works on the server, but not in cases where the same would be done by someone with commit access but no SSH filesystem/shell access (which is likely in future cases). -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] importing/forking from Git
On Tue, Mar 4, 2014 at 7:24 PM, Chad Perrin c...@apotheon.net wrote: Both of those solutions would surely work in this case (as long as the incremental option works on the server, but not in cases where the same would be done by someone with commit access but no SSH filesystem/shell access (which is likely in future cases). If you mean using a hosting service, then I would think the service either provides SSH access or a way transfer existing project repositories to the service's hosts, possibly providing a means to clone from your local Fossil repository to the server. Indeed, making the server side repository a clone of your local repository is probably better. Then there will be no question that you can push further imports to the server repository. ___ 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] importing/forking from Git
On Wed, Mar 05, 2014 at 01:40:49AM -0500, Ron Wilson wrote: On Tue, Mar 4, 2014 at 7:24 PM, Chad Perrin c...@apotheon.net wrote: Both of those solutions would surely work in this case (as long as the incremental option works on the server, but not in cases where the same would be done by someone with commit access but no SSH filesystem/shell access (which is likely in future cases). If you mean using a hosting service, then I would think the service either provides SSH access or a way transfer existing project repositories to the service's hosts, possibly providing a means to clone from your local Fossil repository to the server. I'm talking about a distributed team, where not everyone has SSH shell access or the ability to directly change anything on the filesystem, but they all have commit access to a specific set of repositories. This means, for instance, that they could clone from, and sync with, an existing repository -- but not all could create or delete entire repositories. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
