From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: glibc git - Allow up to 500 commits in a push.
Date: Tue, 29 Mar 2022 17:30:08 -0400 [thread overview]
Message-ID: <xnh77gwiov.fsf@greed.delorie.com> (raw)
In-Reply-To: <acb00b86-5dc5-5e26-cd25-98003053ba0e@redhat.com>
I didn't say we shouldn't do it when appropriate. Just saying I wasn't
looking forward to such a long list of patches to review all at once ;-)
next prev parent reply other threads:[~2022-03-29 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:03 Carlos O'Donell
2022-03-29 20:20 ` DJ Delorie
2022-03-29 21:06 ` Carlos O'Donell
2022-03-29 21:30 ` DJ Delorie [this message]
2022-03-29 21:46 ` Adhemerval Zanella
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=xnh77gwiov.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@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).