unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: alex sassmannshausen <alex.sassmannshausen@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: ping: Fixes for guile.m4
Date: Tue, 22 Jan 2019 07:44:02 +0000	[thread overview]
Message-ID: <CAKdwf2CHe3ZSpwH4=8sz85h7u2gpE8KrM7UHtJJFzDUEktg3xQ@mail.gmail.com> (raw)
In-Reply-To: <20190121144237.GA13893@joshua.dnsalias.com>

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

Hi Mike,

Thanks for taking the time to test, and for the background info. I hadn't
considered the bug tracker!

I'll see if we can get it in there :)

Cheers,

Alex


On Mon, 21 Jan 2019, 14:42 Mike Gran <spk121@yahoo.com wrote:

> On Mon, Jan 21, 2019 at 09:25:17AM +0000, Alex Sassmannshausen wrote:
> > Hello,
> >
> > In December Aleix proposed the following patch to address an issue in
> > guile.m4 whereby guile programs using the autotools infrastructure would
> > not find guile and other tools on distributions such as Ubuntu:
> >
> > http://lists.gnu.org/archive/html/guile-devel/2018-12/msg00002.htm
>
> +1 on getting this incorporated.  I tested the patch and it worked
> for me.
>
> >
> > Guile-Hall, which aims to be a newbie friendly way to create new, and
> > manage existing guile projects, is also affected by this issue.
> >
> > What's the status at this point?  Is there anything that needs to happen
> > before this patch can be merged into Guile?
> >
> > Best wishes,
> >
> > Alex
> >
>
> It isn't so easy to get one-off patches noticed right now, as far
> as I can tell.  Sometimes, you have better luck by putting them
> in the bug-tracker, and then Mark might notice them.
>
> -Mike
>

[-- Attachment #2: Type: text/html, Size: 1948 bytes --]

  reply	other threads:[~2019-01-22  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  9:25 ping: Fixes for guile.m4 Alex Sassmannshausen
2019-01-21 14:42 ` Mike Gran
2019-01-22  7:44   ` alex sassmannshausen [this message]
2019-01-22 23:02   ` moving to gitlab? (was: Re: ping: Fixes for guile.m4) Aleix Conchillo Flaqué
2019-01-23  1:30     ` moving to gitlab? Greg Troxel
2019-01-23  2:12       ` Nala Ginrut
2019-01-23  4:18       ` Aleix Conchillo Flaqué
2019-01-23 14:51         ` Mike Gran
2019-01-25  4:19           ` Amin Bandali

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKdwf2CHe3ZSpwH4=8sz85h7u2gpE8KrM7UHtJJFzDUEktg3xQ@mail.gmail.com' \
    --to=alex.sassmannshausen@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.com \
    /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).