public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Alcides Flores Pineda <alcides.flores@movivendor.com>
To: Per Bothner <per@bothner.com>
Cc: Kawa Community <kawa@sourceware.org>
Subject: Re: Add SRFI-197 Implementation for Kawa
Date: Sun, 07 Mar 2021 16:12:28 -0600	[thread overview]
Message-ID: <87im62396b.fsf@movivendor.com> (raw)
In-Reply-To: <467a5c8f-ef4b-7903-9338-40277cf79eb6@bothner.com> (Per Bothner's message of "Sat, 6 Mar 2021 18:37:33 -0800")

Hello Per:

I have closed the old pull-request !30 (AKA merge-request in GitLab) and
created a new one with the clean changes (!31).

* https://gitlab.com/kashell/Kawa/-/merge_requests/31

This doesn't include the documentation file `doc/kawa.texi`.

Greetings.
-- 
Alcides Flores Pineda.


On mar 06 2021, Per Bothner wrote:

> On 3/6/21 1:50 PM, Alcides Flores Pineda wrote:
>> Hi Per.
>> Thank you very much for your response and feedback.
>> You are right. I do apologize for sendig such a dirty patch.
>> I have now removed the unwanted changes and cleaned it.
>> Here it is in a much better state I hope.
>
> Looks good.
>
> I can apply the diff and check it in, or you can prepare a pull-request,
>
> It should be added to this list:
> http://www.gnu.org/software/kawa/Implemented-SRFIs.html
> for which the source file is doc/kawa.texi
> I can handle that.


  reply	other threads:[~2021-03-07 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  9:04 Alcides Flores Pineda
2021-03-06 19:11 ` Per Bothner
2021-03-06 21:50   ` Alcides Flores Pineda
2021-03-07  2:37     ` Per Bothner
2021-03-07 22:12       ` Alcides Flores Pineda [this message]
2021-04-30 16:36         ` Alcides Flores Pineda
2021-04-30 20:23           ` Per Bothner
2021-03-06  9:15 Alcides Flores Pineda

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=87im62396b.fsf@movivendor.com \
    --to=alcides.flores@movivendor.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.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).