unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: alex.sassmannshausen@gmail.com
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile Hall Release (v0.2)
Date: Sat, 16 Feb 2019 21:10:15 +0800	[thread overview]
Message-ID: <CAPjoZodAZpo9OOEoo+uX_9fSd5K8DqtvmZwY4wjWgdoBH3S-eg@mail.gmail.com> (raw)
In-Reply-To: <878syfyjdw.fsf@gmail.com>

Nice work!
We are moving forward to a bigger community for more contributions now!


Alex Sassmannshausen <alex.sassmannshausen@gmail.com> 于 2019年2月16日周六
21:05写道:

> Hi Neil,
>
> Neil Jerram writes:
>
> > On Fri, 15 Feb 2019 at 16:33, Alex Sassmannshausen
> > <alex.sassmannshausen@gmail.com> wrote:
> >> [...]
> >> Otherwise you can get the code from
> >> https://gitlab.com/a-sassmannshausen/guile-hall/, and build (hopefully)
> >
> > Hi Alex,
> >
> > It's a bit of a side point, but I noticed that your org-mode README is
> > not properly formatted on the Gitlab site, and it looks like it would
> > be if you named it README.org.  Is that something you're already aware
> > of?
>
> Indeed — the project generates itself, and thus far hall defaulted to
> generating README files in org-mode.
>
> I've just pushed a new set of commits that make hall default to
> generating a REDAME.org file, and a symlink to from README to the
> former.
>
> So now this issue should be resolved for Hall itself too :-)
>
> Thanks for the note!
>
> Alex
>
>


  reply	other threads:[~2019-02-16 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 16:18 [ANN] Guile Hall Release (v0.2) Alex Sassmannshausen
2019-02-15 21:29 ` Arne Babenhauserheide
2019-02-16 12:36 ` Neil Jerram
2019-02-16 13:04   ` Alex Sassmannshausen
2019-02-16 13:10     ` Nala Ginrut [this message]
2019-02-17 15:32 ` Mike Gran
2019-02-17 16:40   ` Alex Sassmannshausen

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=CAPjoZodAZpo9OOEoo+uX_9fSd5K8DqtvmZwY4wjWgdoBH3S-eg@mail.gmail.com \
    --to=nalaginrut@gmail.com \
    --cc=alex.sassmannshausen@gmail.com \
    --cc=guile-user@gnu.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).