From: ng0 <ng0@pragmatique.xyz>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 27156@debbugs.gnu.org
Subject: bug#27156: smu
Date: Sat, 3 Jun 2017 19:54:52 +0000 [thread overview]
Message-ID: <20170603195452.b4m4i6d7cujlmj5i@abyayala> (raw)
In-Reply-To: <878tlac91r.fsf@fastmail.com>
Hi,
Marius Bakke transcribed 1.1K bytes:
> ng0 <ng0@pragmatique.xyz> writes:
>
> > This adds smu (simple markup).
> > I've been using this in production for a while.
> >
> > Does it belong in markdown.scm? Technicaly it is not markdown,
> > but it's the closest I could find when I moved it from my
> > package repo to the guix repo.
>
> I think we can rename 'markdown.scm' to 'markup.scm' to make it more
> generic. There doesn't appear to be any users of this module in the tree.
Okay.
> Would you like to give it a go?
I would prefer if someone else did this, I have to work on other
tasks. I could do it if no one else picks it up in a while.
> Also, I'm sure you can get commit access
> if you ask for it, we could use more reviewers ;-)
As I'm currently preparing to get commit access to ftp.gnu.org
for gnURL in the scope of GNUnet, I will have an savannah account soon.
However I don't see the gain in having commit access to Guix.
My work is around Guix and based on Guix and I know how to follow
the standards etc, but any way works for me. If Ricardo or Ludovic
want to give me commit access, it'll happen sooner or later. Last
time we spoke about this 1 year ago I think.
As for reviewing, I'm pretty much busy with my own work. I have the
set of packages I maintain more or less, but I only have time to review
very rarely.
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
next prev parent reply other threads:[~2017-06-03 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 1:03 bug#27156: smu ng0
2017-06-02 22:35 ` Marius Bakke
2017-06-03 19:54 ` ng0 [this message]
2017-06-08 18:34 ` ng0
2017-06-09 22:15 ` Marius Bakke
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=20170603195452.b4m4i6d7cujlmj5i@abyayala \
--to=ng0@pragmatique.xyz \
--cc=27156@debbugs.gnu.org \
--cc=mbakke@fastmail.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.
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).