From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: newlib not building (needs aclocal)
Date: Thu, 24 Feb 2022 10:08:48 +0100 [thread overview]
Message-ID: <YhdLIHoSTGw+158j@calimero.vinschen.de> (raw)
In-Reply-To: <YhcvtT3Df4N9svpP@vapier>
On Feb 24 02:11, Mike Frysinger wrote:
> On 24 Feb 2022 02:07, Mike Frysinger wrote:
> > practically speaking, i don't think topic branches would help that much as
> > you highlight -- the newlib project, and number of projects/devs, is much
> > too small to get a good signal back.
>
> which isn't to say i'm against them. i asked in a previous thread a while
> back about newlib policies around creating branches like this so i could
> push my local state for people to peek at, but didn't get a response. so
> i assumed it was undesired or not allowed.
You can create and destroy topic branches, e.g.
git checkout -b topic/drop-all-32bit-targets
These can be force pushed and generally worked on without generating
mails to newlib-cvs. We're using them in Cygwin as well if something
isn't supposed to go into master just yet.
Corinna
prev parent reply other threads:[~2022-02-24 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:57 Richard Earnshaw
2022-02-22 22:11 ` [PATCH/committed] libgloss: enable maintainer mode support Mike Frysinger
2022-02-23 11:26 ` Richard Earnshaw
2022-02-23 6:01 ` newlib not building (needs aclocal) Brian Inglis
2022-02-23 11:33 ` Richard Earnshaw
2022-02-24 7:07 ` Mike Frysinger
2022-02-24 7:11 ` Mike Frysinger
2022-02-24 9:08 ` Corinna Vinschen [this message]
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=YhdLIHoSTGw+158j@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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 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).