corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Kelly <>
Subject Re: Subscribed
Date Wed, 17 Dec 2014 15:54:11 GMT
> On 17 Dec 2014, at 10:07 pm, jan i <> wrote:
> On Wednesday, December 17, 2014, Peter Kelly <> wrote:
>> The actual URL is
>> <
>> If you do a direct clone of this right now it will give you an error about
>> ‘no branch’. We have two - stable and develop. You can check out as follows:
> is that a problem just now  or something I should talk to infra about ?

I’m not sure if there’s a way to set the default branch on a remote repository from the
client side. Github has an option where you can set this, as do some other git hosting services.

However I don’t thinks it’s strictly necessary that we have a default branch set, and
in fact not doing so forces people to explicitly state whether they want to be on the development
or stable branch. Thus in the instructions we should tell people to issue one of the following

git clone -b develop
git clone -b stable

There’s pros and cons to making one of the the default. We don’t want people committing
to stable directly once we have the build bot up and running, however someone completely new
to the code who just wants to try it out is likely to be best of using the stable branch,
as that is guaranteed to build & work. If their purpose instead is to commit, they should
check out develop.

It’s only an issue the very first time a given person starts working with the repo however,
since it is easy to switch between the branches with ‘git checkout’ after the clone.

Dr. Peter M. Kelly

PGP key: <>
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message