unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Konrad Hinsen <konrad.hinsen@cnrs.fr>,
	guix-science@gnu.org, Lars-Dominik Braun <lars@6xq.net>,
	Ricardo Wurmus <rekado@elephly.net>,
	Romain GARBAGE <romain.garbage@inria.fr>
Subject: Re: Guix-Past moved to Codeberg
Date: Mon, 02 Dec 2024 15:54:19 +0100	[thread overview]
Message-ID: <87ttbmnnj8.fsf@gmail.com> (raw)
In-Reply-To: <878qsyxt11.fsf@gnu.org>

Hi,

On Mon, 02 Dec 2024 at 11:45, Ludovic Courtès <ludo@gnu.org> wrote:

> I’ve now pushed a merge commit such that current ‘master’ is a
> descendant of the “farewell commit”.

Cool!

> Should we do the same on guix-science{,-non-free}?

I would see yes. :-)

Cheers,
simon


  reply	other threads:[~2024-12-02 19:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 13:41 Moving guix-science from GitHub? Ludovic Courtès
2024-09-02 15:07 ` Simon Tournier
2024-09-03  6:12   ` Konrad Hinsen
2024-09-03  8:01     ` Ludovic Courtès
2024-09-03  8:04     ` Ludovic Courtès
2024-09-03  7:52   ` Ludovic Courtès
2024-09-02 15:28 ` Ricardo Wurmus
2024-09-03  7:50   ` Ludovic Courtès
2024-09-03 13:19     ` Simon Tournier
2024-09-05  7:41       ` Ludovic Courtès
2024-10-10 15:18         ` Moving guix-science from GitHub to Codeberg Ludovic Courtès
2024-10-10 21:49           ` Ricardo Wurmus
2024-10-11  6:53             ` Konrad Hinsen
2024-10-11  5:44           ` Lars-Dominik Braun
2024-10-11  7:20             ` Simon Tournier
2024-10-11  9:51             ` Ludovic Courtès
2024-10-11 10:07               ` Lars-Dominik Braun
2024-10-14  7:28                 ` Ludovic Courtès
2024-10-15  8:46                   ` Roel Janssen
2024-10-17 13:27               ` Guix-Science channels moved " Ludovic Courtès
2024-10-18 12:45                 ` Ludovic Courtès
2024-10-18 13:01                   ` Konrad Hinsen
2024-10-22 15:54                     ` Guix-Past " Ludovic Courtès
2024-10-25 12:34                       ` Guix-Jupyter " Ludovic Courtès
2024-11-04 14:26                       ` Guix-Past " Ricardo Wurmus
2024-11-07 15:25                         ` Simon Tournier
2024-11-07 23:15                         ` Ludovic Courtès
2024-11-19 18:17                           ` Ricardo Wurmus
2024-11-20  8:05                             ` Romain GARBAGE
2024-11-21 20:38                               ` Ricardo Wurmus
2024-11-29 16:19                       ` Simon Tournier
2024-12-02 10:45                         ` Ludovic Courtès
2024-12-02 14:54                           ` Simon Tournier [this message]
2024-10-18 13:48                   ` Guix-Science channels " Cayetano Santos
2024-10-19 19:32                     ` Ludovic Courtès
2024-09-04 16:26   ` Moving guix-science from GitHub? Lars-Dominik Braun
2024-09-04 16:33     ` Philippe SWARTVAGHER
2024-09-10 13:39       ` Ludovic Courtès
2024-09-04 18:55 ` Cayetano Santos via Guix-Science

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=87ttbmnnj8.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-science@gnu.org \
    --cc=konrad.hinsen@cnrs.fr \
    --cc=lars@6xq.net \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    --cc=romain.garbage@inria.fr \
    /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).