[fossil-users] Any way to create a branch *not* derived from any other branch?
I'm in the habit of keeping a good number of completely independent projects in a single fossil db. This is a hold over from how I used to use monotone. These are all very small projects that would be annoying to keeping in separate fossil files. When I imported from monotone everything worked as I like and for each of my old projects there exists a separate branch in my fossil db with no common parent. My question is, is there any way to create new branches with no parents? Thanks, Matt -=- ___ 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] Any way to create a branch *not* derived from any other branch?
On Sun, Aug 07, 2011 at 10:21:18AM -0700, Matt Welland wrote: > I'm in the habit of keeping a good number of completely independent projects > in a single fossil db. This is a hold over from how I used to use monotone. > These are all very small projects that would be annoying to keeping in > separate fossil files. When I imported from monotone everything worked as I > like and for each of my old projects there exists a separate branch in my > fossil db with no common parent. > > My question is, is there any way to create new branches with no parents? You could branch from the "Initial Empty Check-in" in trunk. ___ 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] Any way to create a branch *not* derived from any other branch?
On Sun, Aug 7, 2011 at 1:21 PM, Matt Welland wrote: > I'm in the habit of keeping a good number of completely independent > projects in a single fossil db. This is a hold over from how I used to use > monotone. These are all very small projects that would be annoying to > keeping in separate fossil files. Are you familiar with the "fossil all" command. It lets you control a bunch or repos all at once. For example, I normally only my notebook computer when I travel. When I'm at the office, I use desktops. And I have dozens of separate Fossil repos that I keep things in. Just before a trip, I boot up the notebook and type "fossil all sync". That pulls down all the latest changes. Then when I get back, I do "fossil all sync" again, and any changes I made on the road, in any of the separate repositories, are transferred back to the office machines. > When I imported from monotone everything worked as I like and for each of > my old projects there exists a separate branch in my fossil db with no > common parent. > > My question is, is there any way to create new branches with no parents? > There is no easy way - at least not that I can think of. But you might try this: (1) Figure out the project ID of your repo. You can find this by looking in the "config" table of the repo database or on the "stat" page. For example, on http://www.sqlite.org/src/stat we see hat the project ID for SQLite is 2ab58778c2967968b94284e989e43dc11791f548. (2) Do "fossil init newbranch.fossil" to create a new repository. (3) Do "fossil sql -R newbranch.fossil" to get an SQL shell. Then change the project ID in the config table to be the same project ID as your original project as discovered in step 1 above. (4) Push the newbranch.fossil repo into the original project. > > Thanks, > > Matt > -=- > > ___ > 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] Any way to create a branch *not* derived from any other branch?
On Sun, Aug 7, 2011 at 11:47 AM, Richard Hipp wrote: > On Sun, Aug 7, 2011 at 1:21 PM, Matt Welland wrote: > >> I'm in the habit of keeping a good number of completely independent >> projects in a single fossil db. This is a hold over from how I used to use >> monotone. These are all very small projects that would be annoying to >> keeping in separate fossil files. > > > Are you familiar with the "fossil all" command. It lets you control a > bunch or repos all at once. > Apparently not familiar enough! I knew about all rebuild but not all sync. Nice! > For example, I normally only my notebook computer when I travel. When I'm > at the office, I use desktops. And I have dozens of separate Fossil repos > that I keep things in. > > Just before a trip, I boot up the notebook and type "fossil all sync". > That pulls down all the latest changes. Then when I get back, I do "fossil > all sync" again, and any changes I made on the road, in any of the separate > repositories, are transferred back to the office machines. > I will probably migrate to this approach but it is still a significantly bigger hassle than my current methodology. Every time I add a new min-project I have to create new fossils on my central web accessible server and on the other machine where I occasionally work. > > >> When I imported from monotone everything worked as I like and for each of >> my old projects there exists a separate branch in my fossil db with no >> common parent. >> >> My question is, is there any way to create new branches with no parents? >> > > There is no easy way - at least not that I can think of. But you might try > this: > > (1) Figure out the project ID of your repo. You can find this by looking > in the "config" table of the repo database or on the "stat" page. For > example, on http://www.sqlite.org/src/stat we see hat the project ID for > SQLite is 2ab58778c2967968b94284e989e43dc11791f548. > > (2) Do "fossil init newbranch.fossil" to create a new repository. > > (3) Do "fossil sql -R newbranch.fossil" to get an SQL shell. Then change > the project ID in the config table to be the same project ID as your > original project as discovered in step 1 above. > > (4) Push the newbranch.fossil repo into the original project. > > Thanks for this info, it is bit more complicated and not as easily scriptable as I had hoped so I think I'll go with Lluis's suggestion. Although not quite what I wanted I think branching from where the repo was empty should be fine. Thanks! Matt -=- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
