From: "Shawn O. Pearce" <spearce@spearce•org>
To: Leo Razoumov <slonik.az@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [ANNOUCNE] repo - The Multiple Git Repository Tool
Date: Wed, 22 Oct 2008 14:16:05 -0700 [thread overview]
Message-ID: <20081022211605.GX14786@spearce.org> (raw)
In-Reply-To: <ee2a733e0810221255u23aabef2i66d878bcbfa11816@mail.gmail.com>
Leo Razoumov <slonik.az@gmail•com> wrote:
> On 10/22/08, Shawn O. Pearce <spearce@spearce•org> wrote:
> >
> > Google developed two tools, repo and Gerrit, and open sourced them
> > under the Apache License:
> >
> > http://android.git.kernel.org/?p=tools/repo.git
> > http://android.git.kernel.org/?p=tools/gerrit.git
> >
> > git://android.git.kernel.org/tools/repo.git
> > git://android.git.kernel.org/tools/gerrit.git
> >
> > repo is a Python application to bind together Git repositories,
> > something like "git submodule",
>
> Are there any plans to make repo an official git command (e.g.
> git-repo) or merge its functionality with git-submodule?
I currently do not plan on asking Junio to consider making repo part
of git. However, I am also not adverse to it if repo development
slows down and there is sufficient community interest.
--
Shawn.
prev parent reply other threads:[~2008-10-22 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 15:42 [ANNOUCNE] repo - The Multiple Git Repository Tool Shawn O. Pearce
2008-10-22 19:14 ` Junio C Hamano
2008-10-22 21:13 ` Shawn O. Pearce
2008-10-22 23:16 ` Junio C Hamano
2008-10-22 23:17 ` Shawn O. Pearce
2008-10-22 23:46 ` [OT] Amazon wishlist (was Re: [ANNOUCNE] repo - The Multiple Git Repository Tool) Junio C Hamano
2008-10-22 23:52 ` Shawn O. Pearce
2008-10-23 0:45 ` [ANNOUCNE] repo - The Multiple Git Repository Tool David Symonds
2008-10-22 19:55 ` Leo Razoumov
2008-10-22 21:16 ` Shawn O. Pearce [this message]
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=20081022211605.GX14786@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=slonik.az@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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