From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvsimport: add support for new style remote layout
Date: Mon, 04 Jun 2007 09:58:18 +0100 [thread overview]
Message-ID: <4663D42A.7090201@shadowen.org> (raw)
In-Reply-To: <7vvee4n1et.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
>
>> cvsimport creates any branches found in the remote CVS repository
>> in the refs/heads namespace. This makes sense for a repository
>> conversion. When using git as a sane interface to a remote CVS
>> repository, that repository may well remain as the 'master'
>> respository. In this model it makes sense to import the CVS
>> repository into the refs/remotes namespace.
>>
>> Add a new option '-r <remote>' to set the remote name for
>> this import. When this option is specified branches are named
>> refs/remotes/<remote>/branch, with HEAD named as master matching
>> git-clone separate remotes layout. Without branches are placed
>> ion refs/heads, with HEAD named origin as before.
>
> Sounds good. Docs?
Heh, yep if its something wanted then it needs docs. Will drop a couple
of patches following this email. The first is the documentation
updates. The second adds a HEAD link matching git-clone behaviour, and
handily calling cvs HEAD remotes/<remote>/HEAD which seems appropriate.
-apw
next prev parent reply other threads:[~2007-06-04 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 0:56 [PATCH] cvsimport: add support for new style remote layout Andy Whitcroft
2007-05-30 13:24 ` James Bowes
2007-06-03 22:00 ` Junio C Hamano
2007-06-04 8:58 ` Andy Whitcroft [this message]
2007-06-04 9:01 ` [PATCH 1/2] cvsimport: update documentation to include separate remotes option Andy Whitcroft
2007-06-04 9:01 ` [PATCH 2/2] cvsimport: add <remote>/HEAD reference in separate remotes more Andy Whitcroft
2007-06-06 11:52 ` [PATCH] cvsimport: add support for new style remote layout Jeffrey C. Ollie
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=4663D42A.7090201@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).