Comment 8 for bug 104564
Revision history for this message
| Sean Hodges (seanhodges) wrote Re: [Bug 104564] Re: git based import for projects in addition to cvs and svn import | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On Tue, 03 Mar 2009 09:32:19 -0000
Colin Watson <email address hidden> wrote:
> Michael: If it's straightforward, I'd like to be able to name the
> branch to import rather than it being hardcoded to "master".
>
> If you mean imports of multiple branches from a single git
> repository, I don't think that's any more urgent than the same
> feature for other revision control systems supported by Launchpad's
> code import infrastructure. I'm sure we will eventually find a case
> where we need it, but for the meantime imports of just one branch
> will be a major benefit; I don't think we should block git imports on
> multiple-branch imports.
>
I agree, importing from a chosen branch would be the ideal mechanism.
If supporting this on the Launchpad UI would be difficult, it could
maybe default to the master branch, and allow you to override this with
a suffix on the import URL, eg:
git://sean@
Having said that, right now I'd be happy even if it was hard-coded to
master, that would still be better than complete lack of support :)