All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Benjamin Gilbert <bgilbert@backtick.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] master/main branch renaming and bitbake
Date: Thu, 13 May 2021 15:34:00 -0400	[thread overview]
Message-ID: <CADkTA4OA_GBH+YJGNoS0QS-hYp3c1zdnaMVoY=y3V-=3nuAXNw@mail.gmail.com> (raw)
In-Reply-To: <1305.1620933899472438737@lists.openembedded.org>

On Thu, May 13, 2021 at 3:25 PM Benjamin Gilbert <bgilbert@backtick.net> wrote:
>
> On Thu, May 13, 2021 at 12:04 PM, Bruce Ashfield wrote:
>
> Deleting the branch penalizes existing developers, which projects might be willing to do. Git branch names don't usually have any effect on users.
>
> I'm not sure I see the distinction you are trying to draw.
>
> Deleting the branch normally affects people who are in the project's developer community and pay attention to its announcements.  Those folks can then simply update their local checkouts and move on with their lives.  Everyone else just clones the default branch and maybe checks out a particular tag or commit before building a package.  That workflow still works after the default branch is renamed.  Bitbake's additional checks are unusual, and impose a long-term compatibility constraint on upstream projects that they didn't sign up for.

By "user",  I simply meant consumer. (I'm aware of what a developer is
and how they typically work).

We'll agree to disagree on the finer points, since arguing semantics
of good repository management/behaviour is not a good use of time.

Cheers,

Bruce

>
> --Benjamin Gilbert
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

  reply	other threads:[~2021-05-13 19:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:34 master/main branch renaming and bitbake colin walters
2021-05-12 20:40 ` [OE-core] " Alexander Kanavin
2021-05-12 20:43   ` colin walters
2021-05-12 21:17     ` Alexander Kanavin
2021-05-12 21:22       ` Alexander Kanavin
2021-05-13  0:11         ` Andre McCurdy
2021-05-13  7:08           ` Richard Purdie
2021-05-13 13:27             ` colin walters
2021-05-13 13:36               ` Bruce Ashfield
2021-05-13 19:02                 ` Benjamin Gilbert
2021-05-13 19:03                   ` [OE-core] " Bruce Ashfield
2021-05-13 19:24                     ` Benjamin Gilbert
2021-05-13 19:34                       ` Bruce Ashfield [this message]
2021-05-13 19:36                       ` [OE-core] " Alexander Kanavin
2021-05-13 19:44                         ` Konrad Weihmann
2021-05-13 19:54                         ` Benjamin Gilbert
2021-05-13 20:02                           ` [OE-core] " Konrad Weihmann
2021-05-13 20:06                           ` Alexander Kanavin
2021-05-13 20:34                             ` Benjamin Gilbert
2021-05-13 21:04                               ` [OE-core] " Alexander Kanavin
2021-05-13 20:08               ` Richard Purdie
2021-05-13 20:41                 ` Benjamin Gilbert
2021-05-13 21:33                 ` [OE-core] " colin walters
2021-05-13 22:48                   ` Richard Purdie
2021-05-19 16:53                     ` Andre McCurdy
2021-05-13 14:25             ` Peter Kjellerstedt
2021-05-13 20:12               ` Richard Purdie
2021-05-12 20:41 ` Martin Jansa

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='CADkTA4OA_GBH+YJGNoS0QS-hYp3c1zdnaMVoY=y3V-=3nuAXNw@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=bgilbert@backtick.net \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.