From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: xterm: Accept $SHELL even if not in /etc/shells
Date: Fri, 14 Feb 2014 17:59:04 +0100 [thread overview]
Message-ID: <87ha813a1z.fsf@gnu.org> (raw)
In-Reply-To: <20140214123214.GA4956@jocasta.intra> (John Darrington's message of "Fri, 14 Feb 2014 13:32:14 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Fri, Feb 14, 2014 at 11:59:32AM +0100, Ludovic Court??s wrote:
> However, we???re just packaging an existing application. IMO, when we
> find such limitations (it???s really a limitation, and not something that
> makes it completely unusable), we should submit the improvement
> upstream, unless upstream no longer exists (I???m not sure if this is the
> case here.)
>
>
> I think the following are true (please correct me if not):
>
> * Most (all?) the files in gnu/packages/patches fall into the category of
> "limitations" to upstream.
>
> * In principle, those patch files could be directly applied to upstream
> without modification.
I think most of the patches in there are fixes (normally submitted
upstream), or adjustments so that things can build/run in our
environment (patches we don’t want to submit.)
> This being the case, would it not be a good idea, to have some kind of web
> interface to these patch files to make it easy for upstream maintainers to
> fetch them. (perhaps there is sucha page already)
Yes, the page is:
http://www.gnu.org/software/guix/package-list.html
It lists patches and ‘patch snippets’ for each package.
Ludo’.
prev parent reply other threads:[~2014-02-14 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:00 [PATCH] gnu: xterm: Accept $SHELL even if not in /etc/shells Mark H Weaver
2014-02-13 8:07 ` John Darrington
2014-02-13 8:47 ` Mark H Weaver
2014-02-13 11:06 ` John Darrington
2014-02-13 13:12 ` Ludovic Courtès
2014-02-13 16:29 ` Mark H Weaver
2014-02-14 10:59 ` Ludovic Courtès
2014-02-14 12:32 ` John Darrington
2014-02-14 13:30 ` Alex Sassmannshausen
2014-02-14 16:59 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ha813a1z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).