all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 26581@debbugs.gnu.org
Subject: bug#26581: Leftover patch round-up
Date: Fri, 21 Apr 2017 23:19:41 +0200	[thread overview]
Message-ID: <87d1c5a26q.fsf@gnu.org> (raw)
In-Reply-To: <20170420182538.GA11903@jasmine> (Leo Famulari's message of "Thu, 20 Apr 2017 14:25:38 -0400")

Leo Famulari <leo@famulari.name> skribis:

> Let's find the patch files whose filenames are not referenced anywhere,
> except possibly in 'gnu/local.mk':

Woohoo, spring cleanup!  :-)

> Specific notes for each file:
>
> gcc-libiberty-printf-decl.patch: Added in
> b810a85019ab3c4ee1f889d0751b8eb06157dadc and mentioned in the
> commit message but never used, AFAICT. Ludo?

It was used for 5.3 (commit e3d0fcbf7e55e8cbe8d0a1c5a24d73f341d7243b,
which the commit above reinstated; see
<https://gcc.gnu.org/ml/gcc-help/2016-04/msg00039.html>) but useless in
5.4.  So yes, can be removed!

Except for this one:

> gnu/packages/patches/readline-7.0-mingw.patch: Introduced in
> ae12d586275cdd96db23fb01bf840b2055b5b979, but never used. Jan, can you
> take a look?

… it looks like you can go ahead and remove’em all!

Maybe we should add a makefile target to check for stale patches?

Thanks,
Ludo’.

  parent reply	other threads:[~2017-04-21 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 18:25 bug#26581: Leftover patch round-up Leo Famulari
2017-04-20 18:33 ` Leo Famulari
2017-04-21 21:19 ` Ludovic Courtès [this message]
2017-04-21 22:06   ` Leo Famulari
2019-02-04 22:51     ` Leo Famulari

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=87d1c5a26q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26581@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.