unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Julien Lepiller <julien@lepiller.eu>,
	"48637@debbugs.gnu.org" <48637@debbugs.gnu.org>
Subject: [bug#48637] [PATCH] website: Add publications page
Date: Fri, 04 Jun 2021 17:38:18 +0200	[thread overview]
Message-ID: <87eedhprmd.fsf@gnu.org> (raw)
In-Reply-To: <m0kcO6cODXUBz6QdjzneAxhbGnwKu9igNsQMa3W9jtFZAvEA-aFafIDsC_M7Doi-HKLwOAYOlGIdN6mPS6ifFn67EDbYJsznUCJfxecLYdQ=@protonmail.com> (Luis Felipe's message of "Thu, 03 Jun 2021 21:50:18 +0000")

Hi,

Luis Felipe <luis.felipe.la@protonmail.com> skribis:

> So, you mean something like the following would suffice?
>
> https://luis-felipe.gitlab.io/media/2021/06/guix-academic-publications-2021-06-03%2016-39-11.png

Yes.

> I went ahead and added that "publication-scientific?" field and the suggested cap to scientific publications (patch attached). Let me know what you think.

Awesome, pushed!

Thanks for the quick reply and pleasant result!

Ludo’.




      reply	other threads:[~2021-06-04 15:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 23:35 [bug#48637] [PATCH] website: Add publications page Luis Felipe via Guix-patches via
2021-05-25 13:44 ` pelzflorian (Florian Pelz)
2021-05-25 14:37   ` Luis Felipe via Guix-patches via
2021-05-25 18:21     ` pelzflorian (Florian Pelz)
2021-05-25 19:46       ` Luis Felipe via Guix-patches via
2021-05-25 19:58         ` Julien Lepiller
2021-05-25 20:16           ` Luis Felipe via Guix-patches via
2021-05-26  2:03             ` Julien Lepiller
2021-05-26 10:00               ` pelzflorian (Florian Pelz)
2021-05-26 14:06                 ` Luis Felipe via Guix-patches via
2021-05-26 17:41                   ` Julien Lepiller
2021-05-26 18:25                     ` Luis Felipe via Guix-patches via
2021-05-26 18:42                       ` Julien Lepiller
2021-05-26 19:05                         ` Luis Felipe via Guix-patches via
2021-05-25 18:35     ` pelzflorian (Florian Pelz)
2021-05-25 19:14       ` Luis Felipe via Guix-patches via
2021-05-28 11:06 ` Ludovic Courtès
2021-05-28 15:20   ` Luis Felipe via Guix-patches via
2021-05-29 10:25     ` Ludovic Courtès
2021-06-02 19:31   ` Luis Felipe via Guix-patches via
2021-06-02 20:28     ` Julien Lepiller
2021-06-02 21:52       ` Luis Felipe via Guix-patches via
2021-06-02 23:28         ` Julien Lepiller
2021-06-03  9:40     ` Ludovic Courtès
2021-06-03 10:37       ` Julien Lepiller
2021-06-03 13:39         ` Luis Felipe via Guix-patches via
2021-06-03 19:50           ` Luis Felipe via Guix-patches via
2021-06-03 20:37           ` Ludovic Courtès
2021-06-03 21:50             ` Luis Felipe via Guix-patches via
2021-06-04 15:38               ` 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=87eedhprmd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=48637@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=luis.felipe.la@protonmail.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).