unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66454-done@debbugs.gnu.org
Subject: [bug#66454] none
Date: Tue, 31 Oct 2023 20:26:52 +0000	[thread overview]
Message-ID: <CAO+9K5rrPe+ExtasnXB2E8dkjSE19Gk20h3h_JJ_XLXGXSx6MA@mail.gmail.com> (raw)
In-Reply-To: <875y2mr9oo.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hi Maxim,

I've sent October Astronomy updates in separate issue
https://issues.guix.gnu.org/66778

Is there any formal process for commit access and do I need to apply? This
sounds like I can accelerate review process of astro soft an keep them
refreshed.

Regards,
Oleg

On Tue, 31 Oct 2023, 17:19 Maxim Cournoyer, <maxim.cournoyer@gmail.com>
wrote:

> Hi!
>
> Sharlatan Hellseher <sharlatanus@gmail.com> writes:
>
> > Hi,
> >
> > A gentle ping on this issue. Let me know if it needs any modification.
>
> Nice series!  Since you sent it, radio-beam and spectral-cube had a new
> version, so I've updated them.  I've also added 'python-setuptools-scm'
> to their native inputs, otherwise the version metadata was missing from
> their outputs and their version was incorrectly reported as '0.0.0'.
>
> You have cumulated 579 commits thus far; I think you should apply to
> become a committer; this way you could keep the various astrology
> packages updated more easily.
>
> I'd be happy to vouch for you; you clearly put a lot of efforts toward
> producing high-quality packages.
>
> --
> Thanks,
> Maxim
>

[-- Attachment #2: Type: text/html, Size: 1783 bytes --]

  reply	other threads:[~2023-10-31 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  1:34 [bug#66454] [PATCH 0/5] gnu: Add python-spectral-cube Sharlatan Hellseher
2023-10-11  1:39 ` [bug#66454] [PATCH 1/5] gnu: Add python-radio-beam Sharlatan Hellseher
2023-10-11  1:39 ` [bug#66454] [PATCH 2/5] gnu: Add python-pyavm Sharlatan Hellseher
2023-10-11  1:39 ` [bug#66454] [PATCH 3/5] gnu: Add python-pyregion Sharlatan Hellseher
2023-10-11  1:39 ` [bug#66454] [PATCH 4/5] gnu: Add python-aplpy Sharlatan Hellseher
2023-10-11  1:39 ` [bug#66454] [PATCH 5/5] gnu: Add python-spectral-cube Sharlatan Hellseher
2023-10-15 18:17 ` [bug#66454] Sharlatan Hellseher
2023-10-15 18:21   ` [bug#66454] Christopher Baines
2023-10-21 23:00 ` [bug#66454] Sharlatan Hellseher
2023-10-27 17:41 ` [bug#66454] Sharlatan Hellseher
2023-10-31 17:19   ` bug#66454: none Maxim Cournoyer
2023-10-31 20:26     ` Sharlatan Hellseher [this message]
2023-11-01  3:02       ` [bug#66454] none Maxim Cournoyer

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=CAO+9K5rrPe+ExtasnXB2E8dkjSE19Gk20h3h_JJ_XLXGXSx6MA@mail.gmail.com \
    --to=sharlatanus@gmail.com \
    --cc=66454-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.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).