public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: DJ Delorie <dj@redhat.com>
Cc: adhemerval.zanella@linaro.org, fweimer@redhat.com,
	jakub@redhat.com, libc-alpha@sourceware.org, schwab@suse.de,
	joseph@codesourcery.com, maxim.kuvyrkov@linaro.org
Subject: Re: Rename "master" branch to "main" for glibc 2.35 release.
Date: Tue, 1 Feb 2022 10:35:27 +0530	[thread overview]
Message-ID: <70889c7c-2e8c-a5d2-3a03-4fa9d013dab4@gotplt.org> (raw)
In-Reply-To: <xn1r0nxnba.fsf@greed.delorie.com>

On 01/02/2022 09:14, DJ Delorie wrote:
> Siddhesh Poyarekar <siddhesh@gotplt.org> writes:
>> So the idea of trying to eliminate a word or idea from popular
>> vocabulary is not exactly new, we humans do it all the time.
> 
> But there are plenty of examples of words changing for the better, too.
> Who doesn't want to master their fears?  Who isn't a slave to ambition?
> Even POSIX doesn't stay the same forever...

Words don't change, new meanings get added in, often making differences 
murkier.  Take 'fuck' for example; the word has so many meanings but it 
has an underlying flavour that implies a level and type of aggression 
that not many are comfortable with expressing openly.

> But this is neither here nor there; it's our decision in this case, and
> we should make it based on our reasons, not just because someone else
> told us to do it.  And we can do it the way we want to, in a way which
> is best for our users and community, which is why my only real
> opposition is to invalidating old documentation, when keeping it working
> is a trivial thing.

Agreed, I think that's a point (or at least similar) that Joseph raised 
too; there's no strong reason to break links right away, especially for 
a project that has kept libio untouched for fear of breaking programs 
built with gcc 2.95.

Siddhesh

  reply	other threads:[~2022-02-01  5:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 22:32 Carlos O'Donell
2022-01-29 22:45 ` Phil Blundell
2022-01-29 23:33 ` DJ Delorie
2022-01-30  1:35   ` Mike Frysinger
2022-01-30  2:10     ` DJ Delorie
2022-01-30  3:45       ` Mike Frysinger
2022-01-30  2:35 ` Paul Eggert
2022-01-30  5:41   ` Siddhesh Poyarekar
2022-01-31 12:46 ` Florian Weimer
2022-01-31 13:41   ` Andreas Schwab
2022-01-31 14:55   ` Carlos O'Donell
2022-02-01  0:59     ` Dmitry V. Levin
2022-02-01  3:05       ` Carlos O'Donell
2022-01-31 12:50 ` Tulio Magno Quites Machado Filho
2022-01-31 16:19 ` Joseph Myers
2022-01-31 17:59   ` Dan Raymond
2022-01-31 18:04     ` Dan Raymond
2022-01-31 22:49   ` Carlos O'Donell
2022-01-31 23:04     ` Joseph Myers
2022-02-01  3:02       ` Carlos O'Donell
2022-01-31 18:09 ` Adhemerval Zanella
2022-01-31 18:14   ` H.J. Lu
2022-01-31 18:21     ` Adhemerval Zanella
2022-01-31 18:28   ` DJ Delorie
2022-02-01  3:08     ` Siddhesh Poyarekar
2022-02-01  3:44       ` DJ Delorie
2022-02-01  5:05         ` Siddhesh Poyarekar [this message]
2022-02-01  7:25           ` Carlos O'Donell
2022-01-31 20:15   ` Siddhesh Poyarekar
2022-01-31 21:24     ` Adhemerval Zanella
2022-02-01  2:51       ` Siddhesh Poyarekar
2022-02-01  9:49     ` Florian Weimer
2022-02-01 10:26       ` Siddhesh Poyarekar
2022-02-03  5:57 ` Carlos O'Donell

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=70889c7c-2e8c-a5d2-3a03-4fa9d013dab4@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=dj@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=schwab@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).