From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
git@vger.kernel.org, Sebastian Kuzminsky <seb@highlab.com>
Subject: Re: git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug)
Date: Mon, 31 Oct 2005 13:27:26 -0800 [thread overview]
Message-ID: <7vpsplcr7l.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90510311213n565010d6g5586a7484b25da7e@mail.gmail.com> (Martin Langhoff's message of "Tue, 1 Nov 2005 09:13:41 +1300")
Martin Langhoff <martin.langhoff@gmail.com> writes:
> Perhaps git-tla-glue, git-cvs-glue, git-svn-glue, where glue stands
> for importers, exporters, tools, etc?
That sounds sensible. Also I think not having to install xlib
on the repository server is an advantage as you said in your
reply to Linus.
So here is a revised strawman, just to keep things in one place:
git::
Depends on all of the below (may not be necessary).
git-*-glue::
Tools to interoperate with foreign SCM systems,
including importing (i.e. obtaining changes from them)
and exporting (i.e. injecting our changes into them).
git-doc::
Generated documentation from Documentation hierarchy.
git-scm::
Depends on git-gitk and git-core -- people who want just
a self contained SCM can install this and perhaps
git-doc.
git-gitk::
The gitk history browser.
git-core::
The rest. Meant for repository server installation.
next prev parent reply other threads:[~2005-10-31 21:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 20:12 git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) H. Peter Anvin
2005-10-30 20:40 ` Wolfgang Denk
2005-10-30 20:51 ` H. Peter Anvin
2005-10-30 22:16 ` Junio C Hamano
2005-10-30 22:37 ` [PATCH] Do not try installing SVNimport on RPM Junio C Hamano
[not found] ` <43654F4B.30103@zytor.com>
2005-10-30 23:39 ` Junio C Hamano
2005-10-30 22:28 ` git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) Ryan Anderson
2005-10-30 23:01 ` Junio C Hamano
2005-10-31 5:44 ` Junio C Hamano
2005-10-31 6:41 ` Chris Wright
2005-10-31 6:48 ` Junio C Hamano
2005-10-31 15:57 ` H. Peter Anvin
2005-10-31 16:25 ` Linus Torvalds
2005-10-31 16:27 ` H. Peter Anvin
2005-11-01 23:11 ` Horst von Brand
2005-10-31 19:31 ` Junio C Hamano
2005-10-31 19:36 ` H. Peter Anvin
2005-10-31 20:13 ` Martin Langhoff
2005-10-31 20:32 ` Linus Torvalds
2005-10-31 20:44 ` Martin Langhoff
2005-10-31 20:46 ` H. Peter Anvin
2005-10-31 21:31 ` David Lang
2005-10-31 20:39 ` Sebastian Kuzminsky
2005-10-31 21:27 ` Junio C Hamano [this message]
2005-11-05 11:19 ` Package split: Debian Junio C Hamano
2005-11-01 23:15 ` git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) Horst von Brand
2005-11-02 3:36 ` Junio C Hamano
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=7vpsplcr7l.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=martin.langhoff@gmail.com \
--cc=seb@highlab.com \
/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).