From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: merge doc into top-level Makefile
Date: Thu, 11 Nov 2021 17:33:02 -0500 [thread overview]
Message-ID: <YY2aHiZYmB9DYCSp@vapier> (raw)
In-Reply-To: <YYz0VTpzG5PBJ84m@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
On 11 Nov 2021 11:45, Corinna Vinschen wrote:
> On Nov 10 21:07, Mike Frysinger wrote:
> > Avoid a recursive make with this tiny subdir to speed things up a bit.
> > ---
> > newlib/Makefile.am | 29 +-
> > newlib/Makefile.in | 66 +-
> > newlib/configure | 36 +-
> > newlib/configure.ac | 26 +-
> > newlib/doc/Makefile.am | 28 -
> > newlib/doc/Makefile.in | 368 ---
> > newlib/doc/aclocal.m4 | 1012 ---------
> > newlib/doc/configure | 4804 ---------------------------------------
> > newlib/doc/configure.ac | 43 -
> > newlib/doc/local.mk | 20 +
> > 10 files changed, 135 insertions(+), 6297 deletions(-)
> > delete mode 100644 newlib/doc/Makefile.am
> > delete mode 100644 newlib/doc/Makefile.in
> > delete mode 100644 newlib/doc/aclocal.m4
> > delete mode 100755 newlib/doc/configure
> > delete mode 100644 newlib/doc/configure.ac
> > create mode 100644 newlib/doc/local.mk
>
> Patch doesn't apply cleanly to current master. Please rebase.
it isn't a rebase issue. i deleted the hunks for generated files that i removed
since the patch is huge & noisy with them in it via --irreversible-delete. you
could do:
patch -p1 ...
rm newlib/doc/{Makefile.*,*.m4,configure*}
or i can compress & post it.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-11-11 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 2:07 Mike Frysinger
2021-11-11 10:45 ` Corinna Vinschen
2021-11-11 22:33 ` Mike Frysinger [this message]
2021-11-13 5:13 ` Mike Frysinger
2021-11-15 10:38 ` Corinna Vinschen
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=YY2aHiZYmB9DYCSp@vapier \
--to=vapier@gentoo.org \
--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).