Hello all,
I'm currently developing two project tools which are going to be used by the German ReactOS foundation (custom IRC Server and plugin for Jameica - http://www.willuhn.de/products/jameica/). They shall be committed into a public ReactOS SVN repository.
Since I believe that these tools are hardly useful for the average ReactOS developer, I don't want to commit them to our current /trunk/tools directory in the "reactos" repository. Among other disadvantages, every commit to them would trigger a useless BuildBot build, source checkouts would include unnecessary stuff, etc.
As this is generally the case with most of the stuff in /trunk/tools, I'd like to move everything below this directory and the /irc directory into a new repository called "project-tools". We have already done a similar step in the past for the former "web" directory.
Additionally, the "press-media" directory would be a similar candidate for an own "press-media" repository. After these steps, our "reactos" repository would finally contain only OS development related stuff.
For comparison, Wine already keeps its main repository free from unrelated stuff and has several similar repositories (see http://source.winehq.org/git/).
If there are no objections to my idea within the next two weeks, I will proceed and set up "project-tools" and "press-media" repositories (preserving as much SVN history as possible).
Cheers,
Colin
I support that, especially that press-media thing. Thanks.
WBR, Aleksey Bragin.
On Oct 28, 2010, at 12:33 AM, Colin Finck wrote:
Hello all,
I'm currently developing two project tools which are going to be used by the German ReactOS foundation (custom IRC Server and plugin for Jameica - http://www.willuhn.de/products/jameica/). They shall be committed into a public ReactOS SVN repository.
Since I believe that these tools are hardly useful for the average ReactOS developer, I don't want to commit them to our current / trunk/tools directory in the "reactos" repository. Among other disadvantages, every commit to them would trigger a useless BuildBot build, source checkouts would include unnecessary stuff, etc.
As this is generally the case with most of the stuff in /trunk/ tools, I'd like to move everything below this directory and the / irc directory into a new repository called "project-tools". We have already done a similar step in the past for the former "web" directory.
Additionally, the "press-media" directory would be a similar candidate for an own "press-media" repository. After these steps, our "reactos" repository would finally contain only OS development related stuff.
For comparison, Wine already keeps its main repository free from unrelated stuff and has several similar repositories (see http:// source.winehq.org/git/).
If there are no objections to my idea within the next two weeks, I will proceed and set up "project-tools" and "press-media" repositories (preserving as much SVN history as possible).
Cheers,
Colin
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
FYI r49986 broke reg-testing bot.......
On Wed, Oct 27, 2010 at 4:20 PM, Aleksey Bragin aleksey@reactos.org wrote:
I support that, especially that press-media thing. Thanks.
WBR, Aleksey Bragin.
On Oct 28, 2010, at 12:33 AM, Colin Finck wrote:
Hello all,
I'm currently developing two project tools which are going to be used by the German ReactOS foundation (custom IRC Server and plugin for Jameica - http://www.willuhn.de/products/jameica/). They shall be committed into a public ReactOS SVN repository.
Since I believe that these tools are hardly useful for the average ReactOS developer, I don't want to commit them to our current /trunk/tools directory in the "reactos" repository. Among other disadvantages, every commit to them would trigger a useless BuildBot build, source checkouts would include unnecessary stuff, etc.
As this is generally the case with most of the stuff in /trunk/tools, I'd like to move everything below this directory and the /irc directory into a new repository called "project-tools". We have already done a similar step in the past for the former "web" directory.
Additionally, the "press-media" directory would be a similar candidate for an own "press-media" repository. After these steps, our "reactos" repository would finally contain only OS development related stuff.
For comparison, Wine already keeps its main repository free from unrelated stuff and has several similar repositories (see http://source.winehq.org/git/).
If there are no objections to my idea within the next two weeks, I will proceed and set up "project-tools" and "press-media" repositories (preserving as much SVN history as possible).
Cheers,
Colin
Hello all,
Colin Finck mail@colinfinck.de wrote:
If there are no objections to my idea within the next two weeks, I will proceed and set up "project-tools" and "press-media" repositories (preserving as much SVN history as possible).
This repository split has finally happened today.
By using a combination of the tools svndumpfilter and svndumpfilter2 (http://svn.tartarus.org/sgt/svn-tools/svndumpfilter2), I could preserve the complete related SVN history in both repositories. The latter tool even prevented the usual empty revisions that are added during such repository splits (just look at our "web" repo which still has them).
Our CIA.vc reporting scripts have also been updated to the latest version. They now add links to the full ViewVC revision information (e.g. http://svn.reactos.org/svn/project-tools/?view=rev&revision=1232) for all following commits.
Cheers,
Colin
-
Aleksey Bragin -
Colin Finck -
James Tabor