On Mon, Jan 16, 2023 at 02:55:10PM +, Daniel P. Berrangé wrote:
> I'd suggest it is time to libvirt to get on this train and rename our
> default branch to 'main' in all repositories.
>
> There are essentially two options
>
> * Rename 'master' to 'main'
>
> With this, anyone pulling
On 1/16/23 07:55, Daniel P. Berrangé wrote:
I don't recall exactly when it first came up, but it has been a few years
now since the idea of moving away from 'master' as the git default branch
name became a topic in OSS communities. Far from the first mention:
On Tue, Jan 17, 2023 at 09:02:23AM +0100, Martin Kletzander wrote:
> On Mon, Jan 16, 2023 at 02:55:10PM +, Daniel P. Berrangé wrote:
> > I don't recall exactly when it first came up, but it has been a few years
> > now since the idea of moving away from 'master' as the git default branch
> >
On a Monday in 2023, Daniel P. Berrangé wrote:
There are essentially two options
* Rename 'master' to 'main'
With this, anyone pulling from an existing checkout will get an
error telling them that 'master' does not exist. It won't tell
them about 'main', but at least it gives them a
On Tue, Jan 17, 2023 at 09:02:23AM +0100, Martin Kletzander wrote:
> On Mon, Jan 16, 2023 at 02:55:10PM +, Daniel P. Berrangé wrote:
> > I'd suggest it is time to libvirt to get on this train and rename our
> > default branch to 'main' in all repositories.
> >
> > There are essentially two
On Mon, Jan 16, 2023 at 02:55:10PM +, Daniel P. Berrangé wrote:
I don't recall exactly when it first came up, but it has been a few years
now since the idea of moving away from 'master' as the git default branch
name became a topic in OSS communities. Far from the first mention:
I don't recall exactly when it first came up, but it has been a few years
now since the idea of moving away from 'master' as the git default branch
name became a topic in OSS communities. Far from the first mention:
https://sfconservancy.org/news/2020/jun/23/gitbranchname/
Both gitlab.com and