Hello! We already have a number of Git repositories, see <http://git.savannah.gnu.org/cgit/hurd/>.
Now, for publishing last years' GSoC projects etc., we'd need another bunch of 'em: for the projects that create new ``modules'' (procfs, LISP stuff, libchannel, eth-filter, eth-multiplexer, proc_proxy, nsmux, ...) -- I'd like to have theses in separate repositories instead of muddling all of them into the Hurd proper repository. But instead of creating a full-fledged (separate) Git repository for each of the projects, I propose to have a ``dump'' repository in which there are several independent branches (`lisp', `channel', `eth-*', ...) containing the respective files. On these branches, the projects can evolve until they ``are given birth'': until they are published in a stand-alone repository. This is clearly the right thing to do for projects where it is not yet certain if they'll persist at all (proc_proxy, for example); others will be in their top-level repositories right now: procfs for one example. As a sequel, this dump repository is then also meant for developers to publish new stuff they're working on, etc. (unless that is based on other Hurd code, for example, and thus is to be published as a branch of the Hurd repository). Your thoughts? Regards, Thomas
signature.asc
Description: Digital signature