Re: [Savannah-hackers] submission of arch - distributed revision control - savannah.nongnu.org

[Rudy Gevaert]

Hi,

I'm evaluating the project you submitted for approval in Savannah.

Please register your project again including a URL
(could be temporary) where we can find the source code.
The description you give during project registration will be
read by Savannah administrators and not by the general public;
if you are concerned with privacy, you can
send me a copy of the code by e-mail,

We would like to look at your source code, even if it is still
not functional, to help you fix potential legal issues which
would be harder to correct after the project gets approved.
For example, to release your program properly under the GPL,
you should write copyright notices and copying permission statements
at the beginning of every source code file,
as explained in http://www.gnu.org/licenses/gpl-howto.html.

Please register your project once more with the changes mentioned
above.  The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times.  Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,

Rudy
On Thu, May 15, 2003 at 01:00:26AM -0400, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Robert Anderson <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: arch - distributed revision control
> System name: arch
> Type: non-GNU
> 
> Description:
> <a href=\"http://arch.fifthvision.net\";>Arch</a> is a revision control system 
> with features that are ideal for free software and open source projects 
> characterized by widely distributed development, concurrent support of 
> multiple releases, and substantial amounts of development on branches. It is 
> intended to replace CVS and corrects many mis-features of that system.
> 
> Some quick highlights of the feature list are:
> 
>     * distributed repositories -- each hacker or group can host their own 
> branches. There\'s a global (world wide) name-space for lines of development 
> and revisions. Branches can be formed from any repository to any other and 
> merge operations can span repository boundaries without needing to actually 
> duplicate the full contents of a repository at each site.
> 
>     * advanced merging capabilities -- `arch\' has support for various styles 
> of history-sensitive branch merging. The way branches and patch-sets interact 
> with distributed repositories makes it practical to distribute the 
> responsibilities for patch-review and merging.
> 
>     * renames handled -- of course file and directory renames are handled 
> accurately. So are symbolic links and file permissions.
> 
>     * unobtrusive operation -- `arch\' is designed to stay out your way while 
> making changes and rearranging files. It is designed to have a clean and 
> self-documenting command-line interface having the finest characteristics of 
> good Unix tools.
> 
>     * revision libraries -- `arch\' includes tools for building a space 
> efficient library of all past revisions, represented as ordinary file system 
> trees.
> 
> 
> Other Software Required:
> GNU make
> GNU tar
> GNU diff
> GNU patch
> 
> 
> 
> Other Comments:
> 
> 
> 
> 
> _______________________________________________
> Savannah-hackers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/savannah-hackers

-- 
Rudy Gevaert                address@hidden              
Web page                    http:/www.webworm.org
GNU/Linux for schools       http://www.nongnu.org/glms
Savannah hacker             http://savannah.gnu.org