GNOME.org
 

Re: gnome-i18n Digest, Vol 180, Issue 3

I agree with the change but it must be done homogeneously and smooth as possible.
If we have to knock every door and send a bunch of emails for this to happen then let's
do it; we are just asking to not break things up. Maybe we should postpone the
change until everything is set up.

Regards,
Rodrigo

El mié., 24 abr. 2019 a las 11:25, <gnome-i18n-request gnome org> escribió:
Send gnome-i18n mailing list submissions to
        gnome-i18n gnome org

To subscribe or unsubscribe via the World Wide Web, visit
        https://mail.gnome.org/mailman/listinfo/gnome-i18n
or, via email, send a message with subject or body 'help' to
        gnome-i18n-request gnome org

You can reach the person managing the list at
        gnome-i18n-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gnome-i18n digest..."


Today's Topics:

   1. [gnome-calendar] Created branch gnome-3-32
      (Georges Basile Stavracas Neto)
   2. Heads up: Geary mainline development branch renamed to
      `mainline` (Michael Gratton)
   3. Re: Heads up: Geary mainline development branch renamed to
      `mainline` (Daniel Mustieles Garc?a)
   4. Re: Heads up: Geary mainline development branch renamed to
      `mainline` (Andre Klapper)
   5. Re: Heads up: Geary mainline development branch renamed to
      `mainline` (Daniel Mustieles Garc?a)
   6. Re: Heads up: Geary mainline development branch renamed to
      `mainline` (Carmen Bianca Bakker)


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Apr 2019 22:24:49 +0000 (UTC)
From: Georges Basile Stavracas Neto <gbsneto src gnome org>
To: commits-list gnome org
Cc: release-team gnome org,gbsneto src gnome org,gnome-i18n gnome org
Subject: [gnome-calendar] Created branch gnome-3-32
Message-ID: <20190423222449 BF0FA20604 gitlab gnome org>
Keywords: gnome-calendar
Content-Type: text/plain; charset="utf-8"

The branch 'gnome-3-32' was created pointing to:

 f9f46a2... 3.32.1



------------------------------

Message: 2
Date: Wed, 24 Apr 2019 11:46:36 +1000
From: Michael Gratton <mike vee net>
To: gnome-i18n <gnome-i18n gnome org>
Subject: Heads up: Geary mainline development branch renamed to
        `mainline`
Message-ID: <1556070396 3797 0 vee net>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi all,

Just a quick heads-up for people who have use git directly for
traslating Geary: As part of
https://gitlab.gnome.org/GNOME/geary/issues/324 The `master` branch has
been renamed to `mainline`. Same great content (and command line
completion prefix), snazzy new name. :)

So it would be worth doing a `git fetch && git checkout mainline` ASAP,
cherry pick any pending commits you have on the master branch, then
deleting the old branch to avoid committing more changes to it in the
future (`git branch --delete master && git remote prune origin`).

This change happened a few weeks ago, my apologies for not letting
everyone on the list know sooner.

Cheers!
//Mike

--
? Michael Gratton, Percept Wrangler.
? <http://mjog.vee.net/>




------------------------------

Message: 3
Date: Wed, 24 Apr 2019 08:43:02 +0200
From: Daniel Mustieles Garc?a <daniel mustieles gmail com>
To: Michael Gratton <mike vee net>
Cc: gnome-i18n <gnome-i18n gnome org>
Subject: Re: Heads up: Geary mainline development branch renamed to
        `mainline`
Message-ID:
        <CAEy+rQxM0AHCVNhk2-p6wNa-Va6QR9QsCeKCOXvg7R2zRvi6pw mail gmail com>
Content-Type: text/plain; charset="utf-8"

Hi Michael,

As I've already commented in https://gitlab.gnome.org/GNOME/geary/issues/403,
having a "mainline" branch instead of a "master" branch is confusing for
applications like Damned Lies, breaking for example cherry-picks from other
branches to "master" branch, as it doesn't exist.

Stable branches can be named with your own nomenclature (no need to name
them gnome-x.yy) but I would encourage you to keep the "master" branch. It
is the standard name for GNOME's development branches and helps developers
and contributors to identify where to look up the last version of the
source code.

If every GNOME's module begins naming it's "master" branch to whatever the
maintainer wants, this will be a chaos... I don't know where is the
advantage of this renaming (we don't belong to Linux kernel develpment, as
exposed in #324), but coherence across modules should be kept.

Regards.

El mi?., 24 abr. 2019 a las 3:46, Michael Gratton (<mike vee net>) escribi?:

> Hi all,
>
> Just a quick heads-up for people who have use git directly for
> traslating Geary: As part of
> https://gitlab.gnome.org/GNOME/geary/issues/324 The `master` branch has
> been renamed to `mainline`. Same great content (and command line
> completion prefix), snazzy new name. :)
>
> So it would be worth doing a `git fetch && git checkout mainline` ASAP,
> cherry pick any pending commits you have on the master branch, then
> deleting the old branch to avoid committing more changes to it in the
> future (`git branch --delete master && git remote prune origin`).
>
> This change happened a few weeks ago, my apologies for not letting
> everyone on the list know sooner.
>
> Cheers!
> //Mike
>
> --
> ? Michael Gratton, Percept Wrangler.
> ? <http://mjog.vee.net/>
>
>
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.gnome.org/archives/gnome-i18n/attachments/20190424/f9b2a7ca/attachment.html>

------------------------------

Message: 4
Date: Wed, 24 Apr 2019 10:32:56 +0200
From: Andre Klapper <ak-47 gmx net>
To: gnome-i18n gnome org
Subject: Re: Heads up: Geary mainline development branch renamed to
        `mainline`
Message-ID: <e908699a257efd23697513b2a68d91c145173db4 camel gmx net>
Content-Type: text/plain; charset="UTF-8"

On Wed, 2019-04-24 at 08:43 +0200, Daniel Mustieles Garc?a wrote:
> I don't know where is the advantage of this renaming

That is already clearly explained in
https://gitlab.gnome.org/GNOME/geary/issues/324

>  (we don't belong to Linux kernel develpment

And nobody ever said so, so I don't know why it's brought up.

> , as exposed in #324), but coherence across modules should be kept.

I agree that it would be good to consider renaming all master branches.

andre
--
Andre Klapper  |  ak-47 gmx net
https://blogs.gnome.org/aklapper/




------------------------------

Message: 5
Date: Wed, 24 Apr 2019 10:46:21 +0200
From: Daniel Mustieles Garc?a <daniel mustieles gmail com>
To: Andre Klapper <ak-47 gmx net>
Cc: GNOME i18n <gnome-i18n gnome org>
Subject: Re: Heads up: Geary mainline development branch renamed to
        `mainline`
Message-ID:
        <CAEy+rQzJRp=5A19dvJ1XRep7_2G1yqx+-5-5EvE0SjdPQDG2xw mail gmail com>
Content-Type: text/plain; charset="utf-8"

El mi?., 24 abr. 2019 a las 10:33, Andre Klapper (<ak-47 gmx net>) escribi?:

> On Wed, 2019-04-24 at 08:43 +0200, Daniel Mustieles Garc?a wrote:
> > I don't know where is the advantage of this renaming
>
> That is already clearly explained in
> https://gitlab.gnome.org/GNOME/geary/issues/324


Just because "master" implies an "slave" branch? Note that I'm not the only
who disagrees with the change, so maybe the reason is not really clear

>
>
> >  (we don't belong to Linux kernel develpment
>
> And nobody ever said so, so I don't know why it's brought up.
>

Yes, it's mentioned in the issue: "...several projects like Rust, Django
and the Linux kernel..."

>
> > , as exposed in #324), but coherence across modules should be kept.
>
> I agree that it would be good to consider renaming all master branches.
>

Great, but having modules with no standard name for master/trunk/whatever
branch might break applications like Damned Lies, so this rename should be
reconsidered, at least until we decide to rename the whole modulesed's
master branch to another one.

What would happen if every module maintainer decides to rename it's master
branch? It will be a mess... I just think we should keep names homogeously,
don't mind if it's called master, trunk... ;-)

>
> andre
> --
> Andre Klapper  |  ak-47 gmx net
> https://blogs.gnome.org/aklapper/
>
>
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.gnome.org/archives/gnome-i18n/attachments/20190424/00d71be6/attachment.html>

------------------------------

Message: 6
Date: Wed, 24 Apr 2019 11:18:29 +0200
From: Carmen Bianca Bakker <carmen carmenbianca eu>
To: Andre Klapper <ak-47 gmx net>, gnome-i18n gnome org
Subject: Re: Heads up: Geary mainline development branch renamed to
        `mainline`
Message-ID:
        <5d2930be26792ab809ff6dc5e8daefcca32c2524 camel carmenbianca eu>
Content-Type: text/plain; charset="utf-8"

Je mer, 2019-04-24 je 10:32 +0200, Andre Klapper skribis:
> > , as exposed in #324), but coherence across modules should be kept.
>
> I agree that it would be good to consider renaming all master branches.

Then mightn't it be better to bring up the topic with GNOME and/or Git
upstream? Because it would be a bit of a mess if every project could
decide for themselves what to call their master/mainline branch. For
infrastructure reasons, it seems to me that it would be best if the
name of that branch were uniform.

I would like that name to be something other than "master", which is a
bit clunky, inaccurate, and prone to cause offence, but I'd rather have
that than a broken infrastructure.

With kindness,
Carmen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://mail.gnome.org/archives/gnome-i18n/attachments/20190424/477b9ffd/attachment.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
gnome-i18n mailing list
gnome-i18n gnome org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


------------------------------

End of gnome-i18n Digest, Vol 180, Issue 3
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]