all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: david larsson <david.larsson@selfhosted.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 51791@debbugs.gnu.org
Subject: [bug#51791] [PATCH 0/2]: Update guile-bash
Date: Wed, 01 Dec 2021 11:28:55 +0100	[thread overview]
Message-ID: <16a9bbc19db48fb2698d75f30ae6a647@selfhosted.xyz> (raw)
In-Reply-To: <cb85c24cfbbe08819ec2ce5381259059@selfhosted.xyz>

On 2021-12-01 08:20, Ricardo Wurmus wrote:
> Hi David,
> 
> thank you for the update!  What is the upstream status of this patch?
> Has it been sent to upstream?  Is upstream development continuing?
> (That’s what the new home-page implies.)

I have sent a patch a couple weeks ago via sr.ht (my fork is here: 
https://git.sr.ht/~methuselah-0/guile-bash) to the author but no 
response so far.

The latest patch is from 6 years ago so development has probably not 
restarted.

I still think it would be good to change the upstream to sr.ht because 
it very much looks like it's the original author's repository (username 
is kaction) and it has all the change history - versus as it is now 
where I think software heritage is used when building it from source (or 
maybe a cached version on the build farms).

Best regards,
David




  parent reply	other threads:[~2021-12-01 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 13:56 [bug#51791] [PATCH 0/2]: Update guile-bash david larsson
2021-11-12 14:00 ` [bug#51791] [PATCH 1/2]: " david larsson
2021-11-12 14:01 ` david larsson
2021-11-12 15:50 ` [bug#51791] [PATCH 2/2]: " david larsson
2021-11-26 19:16   ` [bug#51791] [PATCH 2/2 v2]: " david larsson
2021-12-01  7:20 ` [bug#51791] [PATCH 0/2]: " Ricardo Wurmus
2021-12-01 10:28 ` david larsson [this message]
2021-12-15 11:54 ` david larsson
2021-12-15 11:55 ` bug#51791: done david larsson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16a9bbc19db48fb2698d75f30ae6a647@selfhosted.xyz \
    --to=david.larsson@selfhosted.xyz \
    --cc=51791@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.