From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>,
Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated (2bea3f2562 -> 6745d692d4)
Date: Fri, 10 May 2024 09:57:46 -0700 [thread overview]
Message-ID: <87ikzly585.fsf@lease-up.com> (raw)
In-Reply-To: <874jb5rghr.fsf@elephly.net>
Hi,
On Fri, May 10 2024, Ricardo Wurmus wrote:
> Christopher Baines writes:
> specific announcements separate from the deluge of emails on
> guix-devel, which I cannot keep up with.
As an alternative, I soon hope to offer a Debbugs clone that publishes
bug reports via NNTP. Any news reader could then subscribe to bug
reports, which is currently not possible. That should reduce the length
and frequency of discussions here to clerical pointers to any relevant
discussions.
> kiasoc5 writes:
> Seeing that these are the only 2 FIXUP commits on the master branch
> history so far, would it make sense to force push and edit the
> history?
I do not know what FIXUP commits are, but generally a Git history should
be broken only for inappropriate or illegal content, such as private
information or offensive imagery.
Kind regards
Felix
next prev parent reply other threads:[~2024-05-10 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171516621153.22775.5117245167398918147@vcs2.savannah.gnu.org>
2024-05-09 9:31 ` branch master updated (2bea3f2562 -> 6745d692d4) Christopher Baines
2024-05-09 20:34 ` Ricardo Wurmus
2024-05-10 11:58 ` Christopher Baines
2024-05-10 12:36 ` Ricardo Wurmus
2024-05-10 16:57 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2024-05-10 21:00 ` Attila Lendvai
2024-05-10 15:28 ` kiasoc5
2024-05-10 16:53 ` Tomas Volf
2024-05-10 20:46 ` Ricardo Wurmus
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=87ikzly585.fsf@lease-up.com \
--to=guix-devel@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=mail@cbaines.net \
--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 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).