git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Seth Robertson <in-gitvger@baka.org>
Cc: git@vger.kernel.org
Subject: Re: Announce gitslave - manage a superproject with slave repositories
Date: Tue, 21 Sep 2010 14:47:44 -0700 (PDT)	[thread overview]
Message-ID: <m3r5gmkbw0.fsf@localhost.localdomain> (raw)
In-Reply-To: <201009210139.o8L1d1iY026728@no.baka.org>

Seth Robertson <in-gitvger@baka.org> writes:

> I'd like to announce the first public version of gitslave.
> 
> gitslave creates a group of related repositories all of which are
> concurrently developed on and on which all git operations should
> operate, so when you branch, each repository in the project is
> branched in turn.  Similarly when you commit, push, pull, merge,
> tag, checkout, status, log, etc; each git command will run on the
> superproject and all slave repositories in turn.  This sort of
> activity may be very familiar to CVS users and to a lesser extent
> subversion users where it was fairly normal to assemble a
> superproject in just this way.
[...]

> http://gitslave.sourceforge.net/
> 
> Current release as of 2010-09-20: 1.0.0
> http://sourceforge.net/projects/gitslave/files/gitslave-1.0.0.tar.gz/download

Could you please add information about this project to
InterfacesFrontendsAndTools page on Git Wiki:
  https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools

Somewhere in neighbourhood of 'repo' or 'git-subtree' could be good.

Thanks in advance.
-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2010-09-21 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  1:39 Announce gitslave - manage a superproject with slave repositories Seth Robertson
2010-09-21 21:47 ` Jakub Narebski [this message]
2010-09-23 22:49 ` Thomas Adam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3r5gmkbw0.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=in-gitvger@baka.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).