Thread: [CEDET-devel] Migration to bazaar
Brought to you by:
zappo
From: Lluís <xs...@gm...> - 2010-08-19 15:31:36
Attachments:
migrate.sh
cvs2bzr.opt
|
"sourceforge writes: > I've fixed the permissions on your repository. So, finally, sourceforge fixed the issue that prevented the creation of bazaar branches. I've migrated all the CVS history, which has produced: branch trunk now has 8166 revisions and 0 tags branch TAG.FIXUP now has 1605 revisions and 1 tag branch cedet-1p0beta1 now has 3523 revisions and 0 tags branch cedet-1p0beta2 now has 4041 revisions and 0 tags branch cedet-1p0pre1 now has 4416 revisions and 0 tags branch cedet-1p0pre2 now has 4466 revisions and 0 tags branch cedet-1p0pre3 now has 4514 revisions and 0 tags branch cedet-1p0pre4 now has 4974 revisions and 0 tags branch cedet-1p0pre5 now has 5999 revisions and 0 tags branch cedet-1p0pre6 now has 6916 revisions and 0 tags branch cedet-1p0pre7 now has 7839 revisions and 0 tags branch unlabeled-1.11.2 now has 1865 revisions and 0 tags branch unlabeled-1.13.2 now has 2000 revisions and 0 tags branch unlabeled-1.138.2 now has 2037 revisions and 0 tags branch unlabeled-1.16.2 now has 1946 revisions and 0 tags branch unlabeled-1.17.2 now has 1990 revisions and 0 tags branch unlabeled-1.19.2 now has 1865 revisions and 0 tags branch unlabeled-1.30.2 now has 1959 revisions and 0 tags branch unlabeled-1.33.2 now has 1933 revisions and 0 tags branch unlabeled-1.39.2 now has 1969 revisions and 0 tags branch unlabeled-1.4.2 now has 1785 revisions and 0 tags branch unlabeled-1.5.2 now has 1884 revisions and 0 tags branch unlabeled-1.50.2 now has 2017 revisions and 0 tags branch unlabeled-1.55.2 now has 2041 revisions and 0 tags branch unlabeled-1.57.2 now has 1986 revisions and 0 tags branch unlabeled-1.7.2 now has 1927 revisions and 0 tags branch unlabeled-1.87.2 now has 2046 revisions and 0 tags branch v1_4 now has 2037 revisions and 0 tags branch v1p4 now has 2325 revisions and 0 tags branch wisent now has 1493 revisions and 0 tags And I've also uploaded the 'trunk' branch, which can now be accessed at: bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/trunk bzr+ssh://USE...@ce.../bzrroot/cedet/trunk So now, 2 things: - which (if any) of these branches should also be ported to bazaar (I think last time I asked Eric the answer was "none") - maybe we should agree on naming and directory organization conventions, like: http://bzr.savannah.gnu.org/r/emacs/README Please do not commit into the bzr repository until a scheme has been agreed on. Once we all agree on the state of the conversion, the CVS repository should be left in read-only mode, and development shifted into the bzr repository. If you want to tinker with the conversion by yourself, have a look at the attached files (needs cvs2bzr and the fastimport plugin for bazaar). Lluis |
From: Lluís <xs...@gm...> - 2010-08-20 13:49:37
|
Eric M Ludlam writes: >> Once we all agree on the state of the conversion, the CVS repository should be >> left in read-only mode, and development shifted into the bzr repository. > Perhaps I should tag and release a CEDET 1.0 in CVS this weekend, as it > seems stable enough and has had plenty of preview releases. That would > free the bzr repository to move into the new file naming conventions > needed by Emacs. > I don't have any pending changes left. All right then. If nobody has fixes to commit, let's just tag current state as the 1.0 release. Feel free to commit changes to the CVS. If it gets changes I'll just migrate repositories again, which is pretty painlessly automated with the scripts I sent to the list. Once having this, the development process and branch organization should be documented somewhere (aka web page or a wiki). We could just refer the developer to http://www.emacswiki.org/emacs/BzrQuickStartForEmacsDevs and highlight just the differences on URLs. Thinking of the web, the current tree is organized as: cedet-build.el cedet-ediff.el cedet-update-changelog.el cedet-update-version.el cogre/ common/ contrib/ CVS/ ede/ eieio/ Emacs2CEDET gettodos.sh* INSTALL Makefile Makefile.wwwinfo PRERELEASE_CHECKLIST quickpeek/ semantic/ speedbar/ srecode/ testdist.sh* testprojects/ tests/ USING_CEDET_FROM_CVS www/ And I think the part concerning the web page (is it only www/?) should be seggregated onto a different repository/branch, which brings me again to the question of how the repository should be organized. ---- on bazaar ---- Disclaimer: You'll probably have a better explanation somewhere else. Here's a link for the CVS savvy: http://wiki.bazaar.canonical.com/BzrForCVSUsers Taking a step back, I'll try to summarize my grasps on how bazaar works. The 3 basic concepts about organization (let alone commits) are: - repository - branch - tag A repository is just a directory used as storage space for changesets (commits), which can be created with 'bzr init-repo'. In fact, we will create such repositories on the central server with 'bzr init-repo --no-trees', but an explanation of why is out of the scope of this mail. A branch is what developers will work with, much in the same fashion as subversion (one directory for each branch). Branches also have some information about the parent branch, such that one can understand how branches are related to each other. Such branches are created with 'bzr init'. If multiple branches are created as subdirectories of a repository (even if they are deeply nested), they will all share the same storage. This makes sense for branches that are related, as much of the changeset history will be exactly the same among such branches. A tag is just a user-specified name for a changeset in a branch, and tag infomation can be passed onto other branches when these are merged. ---- on bazaar ---- So, this is all to say that the bzr in SF should be organized in, at least, two repositories (r): www/ [r] code/ [r] (or any other name) And branches (b) could then be something like: www/ [r+b] (there will probably be just a single branch for the web) code/ [r] code/trunk/ [b] At first only the 'code/trunk/' branch will be available, but it is recommended to start a new branch for each non-trivial set of changes. Those features requiring long development/integration time that must be available to multiple developers should then be published on the SF repository, such that they can all be developed separately. Again, have a look at: http://www.emacswiki.org/emacs/BzrQuickStartForEmacsDevs Summarizing: - if you have fixes to current code submit these before Eric tags the repository - if you agree on having two repositories, I'll try to seggregate the imported history from whatever is related to the web page - Eric, which are the files/directories related to web page management? Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth |
From: Eric M. L. <er...@si...> - 2010-08-23 01:51:00
|
On 08/20/2010 09:49 AM, Lluís wrote: > Eric M Ludlam writes: >>> Once we all agree on the state of the conversion, the CVS repository should be >>> left in read-only mode, and development shifted into the bzr repository. > >> Perhaps I should tag and release a CEDET 1.0 in CVS this weekend, as it >> seems stable enough and has had plenty of preview releases. That would >> free the bzr repository to move into the new file naming conventions >> needed by Emacs. > >> I don't have any pending changes left. > > All right then. If nobody has fixes to commit, let's just tag current state as > the 1.0 release. It is now tagged. Unfortunately, I was unable to get XEmacs working. :( > Feel free to commit changes to the CVS. If it gets changes I'll just migrate > repositories again, which is pretty painlessly automated with the scripts I sent > to the list. There have been a few small changes. > Once having this, the development process and branch organization should be > documented somewhere (aka web page or a wiki). We could just refer the developer > to http://www.emacswiki.org/emacs/BzrQuickStartForEmacsDevs and highlight just > the differences on URLs. I think makes sense to copy until we start to deviate. I would assume that the cross merging process would result in some differences. > Thinking of the web, the current tree is organized as: > cedet-build.el > cedet-ediff.el > cedet-update-changelog.el > cedet-update-version.el > cogre/ > common/ > contrib/ > CVS/ > ede/ > eieio/ > Emacs2CEDET > gettodos.sh* > INSTALL > Makefile > Makefile.wwwinfo > PRERELEASE_CHECKLIST > quickpeek/ > semantic/ > speedbar/ > srecode/ > testdist.sh* > testprojects/ > tests/ > USING_CEDET_FROM_CVS > www/ > > And I think the part concerning the web page (is it only www/?) should be > seggregated onto a different repository/branch, which brings me again to the > question of how the repository should be organized. I agree about www being seperate. The www dir is the only one that matters. The Makefile.wwwinfo is old and crufty. I don't know how renames work in bzr, but would it make sense to have the CVS type filesystem in one repository, and the fully renamed to Emacs variant in a different one? Then CEDET 1.0.1 could be cut from BZR if small changes are needed there. In addition, not all parts of CEDET's current file system will move to the Emacs style filesystem. For example, quickpeek (very old) and speedbar (not changing) should be retired from future CEDET releases. > ---- on bazaar ---- Thanks for all the extra information. Learning this will be my next project. Thanks Eric |
From: Lluís <xs...@gm...> - 2010-08-23 14:56:14
|
Eric M Ludlam writes: >> All right then. If nobody has fixes to commit, let's just tag current state as >> the 1.0 release. > It is now tagged. Unfortunately, I was unable to get XEmacs working. :( Well there is no big rush for tagging the 1.0 release. Just keep working as you would normally do. The only difference is that development will shift from CVS to BZR, but this does not mean that 1.0 must be realeased before the migration. [...] > I don't know how renames work in bzr, As far as I know file/directory renames are stored in the history, so nothing is lost through renaming. > but would it make sense to have the CVS type filesystem in one repository, and > the fully renamed to Emacs variant in a different one? Then CEDET 1.0.1 could > be cut from BZR if small changes are needed there. If I understood you well, this is exactly my intention. First, migrate from current CVS to separate www/ and code/trunk/. Once everything is in place I'll just create a new branch (e.g., code/emacs-style-rename/) and work from there, so no development on trunk nor any other branch will be affected by my changes until we merge them into trunk. BTW, homogenizing with upstream emacs is not only a matter of renaming files. There are also the changes on menu layouts and start/stop routines for each cedet subsystem. Is there a plan against or in favour of these changes? > In addition, not all parts of CEDET's current file system will move to > the Emacs style filesystem. For example, quickpeek (very old) and > speedbar (not changing) should be retired from future CEDET releases. Then I'll just delete those files. > Thanks for all the extra information. Learning this will be my next > project. http://doc.bazaar.canonical.com/bzr.2.2/en/ http://sourceforge.net/apps/trac/sourceforge/wiki/Bazaar Whenever you start using bzr in sourceforge, remember to set who are you according to sourceforge policy: bzr whoami "USERNAME <USE...@us...>" Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth |
From: Alex O. <al...@gm...> - 2010-08-25 06:44:41
|
Hi Eric I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to write official announcement about it - this is huge milestone for the project -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Alex O. <al...@gm...> - 2010-08-25 11:49:27
|
Re all I downloaded release version and compiled it without errors, but 'make utest' is failed with following log: ......... * Java tests... All Java tests passed. * Javascript tests... Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 * ERROR: (error "Buffer javascripttest.js was not set up for parsing") to debug this test point, execute: semantic-utest-main ** Exiting Test Suite. ** I run cedet-utest from emacs, and it finished without errors, although it reported, that it couldn't find graphviz (I have it installed already) I use 64-bit Debian with emacs-snapshot (GNU Emacs 24.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-08-21 on elegiac, modified by Debian) Eric M. Ludlam at "Wed, 25 Aug 2010 07:28:50 -0400" wrote: EML> On 08/25/2010 02:47 AM, Alex Ott wrote: >> Hi Eric >> >> I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to >> write official announcement about it - this is huge milestone for the project >> EML> I agree. I wanted to download it to my work computers to try it out to EML> double check everything, but didn't get that far. :( Fortunately I have EML> a big block of time to work this stuff out tonight. Woo! -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Alex O. <al...@gm...> - 2010-08-26 11:32:25
|
I was able to find this error - we need to add following line to make it working with emacs 24 ;;;###autoload (add-hook 'js-mode-hook 'wisent-javascript-setup-parser) I also wants to add following lines, because I personally use js2-mode for javascript: ;;;###autoload (add-hook 'js2-mode-hook 'wisent-javascript-setup-parser) But I couldn't commit to bzr repository, although I able to fetch data using my sf name bzr: ERROR: Cannot lock LockDir(chroot-47170089440528:///bzrroot/cedet/code/trunk/.bzr/branch/lock): Permission denied: "/bzrroot/cedet/code/trunk/.bzr/branch/lock/d9amve8nya.tmp": [Errno 13] Permission denied: '/bzrroot/cedet/code/trunk/.bzr/branch/lock/d9amve8nya.tmp' Eric M. Ludlam at "Wed, 25 Aug 2010 18:17:24 -0400" wrote: EML> Didn't the javascript mode recently get shuffled about? I'd guess that EML> semantic/wisent/wisent-javascript.el, at the very end, needs a different hook installed. EML> I don't know where the below warnings about 'interactively' are coming from. EML> The graphviz test is EML> M-x cedet-graphviz-dot-version-check EML> It may be that a path is different when you run make vs start Emacs normally? EML> I haven't done any testing myself with Emacs 23.3 nor 24.0. My main hope in wrapping this EML> up is for those with earlier Emacsen (22 and 23). After the rename project, it will EML> certainly target 23.2 and 24+ releases of Emacs. EML> Eric EML> On 08/25/2010 07:52 AM, Alex Ott wrote: >> Re all >> >> I downloaded release version and compiled it without errors, but 'make >> utest' is failed with following log: >> >> >> ......... >> * Java tests... >> All Java tests passed. >> * Javascript tests... >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 >> * ERROR: (error "Buffer javascripttest.js was not set up for parsing") >> to debug this test point, execute: >> semantic-utest-main >> >> ** Exiting Test Suite. ** >> >> I run cedet-utest from emacs, and it finished without errors, although it >> reported, that it couldn't find graphviz (I have it installed already) >> >> I use 64-bit Debian with emacs-snapshot (GNU Emacs 24.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-08-21 on elegiac, modified by Debian) >> >> >> >> Eric M. Ludlam at "Wed, 25 Aug 2010 07:28:50 -0400" wrote: >> EML> On 08/25/2010 02:47 AM, Alex Ott wrote: >> >> Hi Eric >> >> >> >> I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to >> >> write official announcement about it - this is huge milestone for the project >> >> >> >> EML> I agree. I wanted to download it to my work computers to try it out to >> EML> double check everything, but didn't get that far. :( Fortunately I have >> EML> a big block of time to work this stuff out tonight. Woo! >> >> -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Eric M. L. <er...@si...> - 2010-08-24 01:25:58
|
On 08/23/2010 10:56 AM, Lluís wrote: > Eric M Ludlam writes: >>> All right then. If nobody has fixes to commit, let's just tag current state as >>> the 1.0 release. > >> It is now tagged. Unfortunately, I was unable to get XEmacs working. :( > > Well there is no big rush for tagging the 1.0 release. Just keep working as you > would normally do. Being the lazy guy I am, having a motivation to get something done is always helpful. ;) >> but would it make sense to have the CVS type filesystem in one repository, and >> the fully renamed to Emacs variant in a different one? Then CEDET 1.0.1 could >> be cut from BZR if small changes are needed there. > > If I understood you well, this is exactly my intention. First, migrate from > current CVS to separate www/ and code/trunk/. > > Once everything is in place I'll just create a new branch (e.g., > code/emacs-style-rename/) and work from there, so no development on trunk nor > any other branch will be affected by my changes until we merge them into trunk. I was thinking that there would be some permanent branch for the current naming scheme and the next one, but if the histories work well, it probably doesn't make much difference. > BTW, homogenizing with upstream emacs is not only a matter of renaming > files. There are also the changes on menu layouts and start/stop routines for > each cedet subsystem. Is there a plan against or in favour of these changes? I would like to move to a system as close to what Emacs does as possible to minimize maintenance, and adoption of features from CEDET up to Emacs. Thanks! Eric |
From: Eric M. L. <er...@si...> - 2010-08-25 11:28:57
|
On 08/25/2010 02:47 AM, Alex Ott wrote: > Hi Eric > > I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to > write official announcement about it - this is huge milestone for the project > I agree. I wanted to download it to my work computers to try it out to double check everything, but didn't get that far. :( Fortunately I have a big block of time to work this stuff out tonight. Woo! Eric |
From: Eric M. L. <er...@si...> - 2010-08-25 22:44:13
|
Didn't the javascript mode recently get shuffled about? I'd guess that semantic/wisent/wisent-javascript.el, at the very end, needs a different hook installed. I don't know where the below warnings about 'interactively' are coming from. The graphviz test is M-x cedet-graphviz-dot-version-check It may be that a path is different when you run make vs start Emacs normally? I haven't done any testing myself with Emacs 23.3 nor 24.0. My main hope in wrapping this up is for those with earlier Emacsen (22 and 23). After the rename project, it will certainly target 23.2 and 24+ releases of Emacs. Eric On 08/25/2010 07:52 AM, Alex Ott wrote: > Re all > > I downloaded release version and compiled it without errors, but 'make > utest' is failed with following log: > > > ......... > * Java tests... > All Java tests passed. > * Javascript tests... > Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > * ERROR: (error "Buffer javascripttest.js was not set up for parsing") > to debug this test point, execute: > semantic-utest-main > > ** Exiting Test Suite. ** > > I run cedet-utest from emacs, and it finished without errors, although it > reported, that it couldn't find graphviz (I have it installed already) > > I use 64-bit Debian with emacs-snapshot (GNU Emacs 24.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-08-21 on elegiac, modified by Debian) > > > > Eric M. Ludlam at "Wed, 25 Aug 2010 07:28:50 -0400" wrote: > EML> On 08/25/2010 02:47 AM, Alex Ott wrote: > >> Hi Eric > >> > >> I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to > >> write official announcement about it - this is huge milestone for the project > >> > > EML> I agree. I wanted to download it to my work computers to try it out to > EML> double check everything, but didn't get that far. :( Fortunately I have > EML> a big block of time to work this stuff out tonight. Woo! > > |
From: Eric M. L. <er...@si...> - 2010-08-27 12:35:39
|
Hi Alex, Thanks. I slipstreamed that in. I'm trying to put the announcement together. How would you label CEDET 1.0 support for Emacs 24.0? I know it works, but are there Caveats, or extra installation steps? Thanks Eric On 08/26/2010 07:35 AM, Alex Ott wrote: > I was able to find this error - we need to add following line to make it > working with emacs 24 > > ;;;###autoload > (add-hook 'js-mode-hook 'wisent-javascript-setup-parser) > > I also wants to add following lines, because I personally use js2-mode for > javascript: > > ;;;###autoload > (add-hook 'js2-mode-hook 'wisent-javascript-setup-parser) > > But I couldn't commit to bzr repository, although I able to fetch data > using my sf name > > bzr: ERROR: Cannot lock LockDir(chroot-47170089440528:///bzrroot/cedet/code/trunk/.bzr/branch/lock): Permission denied: "/bzrroot/cedet/code/trunk/.bzr/branch/lock/d9amve8nya.tmp": [Errno 13] Permission denied: '/bzrroot/cedet/code/trunk/.bzr/branch/lock/d9amve8nya.tmp' > > > > Eric M. Ludlam at "Wed, 25 Aug 2010 18:17:24 -0400" wrote: > EML> Didn't the javascript mode recently get shuffled about? I'd guess that > EML> semantic/wisent/wisent-javascript.el, at the very end, needs a different hook installed. > > EML> I don't know where the below warnings about 'interactively' are coming from. > > EML> The graphviz test is > > EML> M-x cedet-graphviz-dot-version-check > > EML> It may be that a path is different when you run make vs start Emacs normally? > > EML> I haven't done any testing myself with Emacs 23.3 nor 24.0. My main hope in wrapping this > EML> up is for those with earlier Emacsen (22 and 23). After the rename project, it will > EML> certainly target 23.2 and 24+ releases of Emacs. > > EML> Eric > > EML> On 08/25/2010 07:52 AM, Alex Ott wrote: > >> Re all > >> > >> I downloaded release version and compiled it without errors, but 'make > >> utest' is failed with following log: > >> > >> > >> ......... > >> * Java tests... > >> All Java tests passed. > >> * Javascript tests... > >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > >> Warning: cedet-called-interactively-p called with 0 arguments, but requires 1 > >> * ERROR: (error "Buffer javascripttest.js was not set up for parsing") > >> to debug this test point, execute: > >> semantic-utest-main > >> > >> ** Exiting Test Suite. ** > >> > >> I run cedet-utest from emacs, and it finished without errors, although it > >> reported, that it couldn't find graphviz (I have it installed already) > >> > >> I use 64-bit Debian with emacs-snapshot (GNU Emacs 24.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-08-21 on elegiac, modified by Debian) > >> > >> > >> > >> Eric M. Ludlam at "Wed, 25 Aug 2010 07:28:50 -0400" wrote: > >> EML> On 08/25/2010 02:47 AM, Alex Ott wrote: > >> >> Hi Eric > >> >> > >> >> I see, that CEDET 1.0 is uploaded to SF - I think, that it good idea to > >> >> write official announcement about it - this is huge milestone for the project > >> >> > >> > >> EML> I agree. I wanted to download it to my work computers to try it out to > >> EML> double check everything, but didn't get that far. :( Fortunately I have > >> EML> a big block of time to work this stuff out tonight. Woo! > >> > >> > > |
From: Alex O. <al...@gm...> - 2010-08-27 12:49:39
|
Re Eric M. Ludlam at "Fri, 27 Aug 2010 08:35:31 -0400" wrote: EML> Hi Alex, EML> Thanks. I slipstreamed that in. EML> I'm trying to put the announcement together. How would you label CEDET 1.0 support for EML> Emacs 24.0? I know it works, but are there Caveats, or extra installation steps? I used standard compilation commands, without extra packages, etc. The only problem was a problem with JS (I just remembered, that in emacs-devel was discussion of how to rename javascript-mode), and this strange problem with graphviz, that isn't reproducible when running 'make utest' -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Alex O. <al...@gm...> - 2010-08-27 12:54:01
|
Hello Lluis I want to ask you about access rights for CEDET repository - I get an error, when trying to commit to repository, although I able to retrieve data using my sf name (ottalex) and ssh key -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Lluís <xs...@gm...> - 2010-08-27 13:16:18
|
Alex Ott writes: > Hello Lluis > I want to ask you about access rights for CEDET repository - I get an > error, when trying to commit to repository, although I able to retrieve > data using my sf name (ottalex) and ssh key Right! I forgot to add group write permissions when I created the directories. It should work now :) Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth |
From: Alex O. <al...@gm...> - 2010-08-27 13:18:53
|
Thank you Lluís at "Fri, 27 Aug 2010 15:16:04 +0200" wrote: L> Alex Ott writes: >> Hello Lluis >> I want to ask you about access rights for CEDET repository - I get an >> error, when trying to commit to repository, although I able to retrieve >> data using my sf name (ottalex) and ssh key L> Right! I forgot to add group write permissions when I created the L> directories. It should work now :) L> Lluis -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ |
From: Eric M. L. <er...@si...> - 2010-08-19 23:33:08
|
On 08/19/2010 11:31 AM, Lluís wrote: > "sourceforge writes: >> I've fixed the permissions on your repository. > > So, finally, sourceforge fixed the issue that prevented the creation of bazaar > branches. Great! > I've migrated all the CVS history, which has produced: > > branch trunk now has 8166 revisions and 0 tags > branch TAG.FIXUP now has 1605 revisions and 1 tag > branch cedet-1p0beta1 now has 3523 revisions and 0 tags > branch cedet-1p0beta2 now has 4041 revisions and 0 tags > branch cedet-1p0pre1 now has 4416 revisions and 0 tags > branch cedet-1p0pre2 now has 4466 revisions and 0 tags > branch cedet-1p0pre3 now has 4514 revisions and 0 tags [...] > > And I've also uploaded the 'trunk' branch, which can now be accessed at: > bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/trunk > bzr+ssh://USE...@ce.../bzrroot/cedet/trunk Thanks! > So now, 2 things: > - which (if any) of these branches should also be ported to bazaar (I think > last time I asked Eric the answer was "none") So long as CVS is around, I don't see the needs for all those branches. > - maybe we should agree on naming and directory organization conventions, > like: > http://bzr.savannah.gnu.org/r/emacs/README I think the Emacs scheme and the CEDET scheme should be similar. Whatever it is should make the cross merges easier, and I don't have much background here. > Please do not commit into the bzr repository until a scheme has been agreed on. > > Once we all agree on the state of the conversion, the CVS repository should be > left in read-only mode, and development shifted into the bzr repository. Perhaps I should tag and release a CEDET 1.0 in CVS this weekend, as it seems stable enough and has had plenty of preview releases. That would free the bzr repository to move into the new file naming conventions needed by Emacs. I don't have any pending changes left. > If you want to tinker with the conversion by yourself, have a look at the > attached files (needs cvs2bzr and the fastimport plugin for bazaar). Thanks. Eric |