unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 39648@debbugs.gnu.org
Cc: Danny Milosavljevic <dannym@scratchpost.org>,
	Raghav Gururajan <raghavgururajan@disroot.org>
Subject: bug#39648: Reverse my commits on GNOME meta-package
Date: Mon, 17 Feb 2020 20:02:59 +0100	[thread overview]
Message-ID: <875zg56nq4.fsf@nckx> (raw)
In-Reply-To: <6bad163b0ed969c5c1117f9fa7446631060a8d4d.camel@disroot.org>

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

Raghav Gururajan 写道:
> Could you please reverse my following commits:
>
> 1) d36fa50fbf8169018193774782fd21f1b13b9c0e
>
> 2) 7922b6f795eb575084546ec9bfb9d40508a9378e
>
> 3) 8d8c6bffc528b60574f84620bd6c3ee9bfa1173f
>
> 4) a8cda7f57992e9ce9ae4a694eba54e3eab42c39b

Copy-pasted from #guix:

Whoa there, that's drastic, let's put that on hold.

The first two only add packages (did they break anything? what?), 
the third has no effect on packages if your commit message is 
accurate.

The fourth is the only one that removes packages, and even that 
might be better tweaked (this time: with comments noting what each 
non-core package brings to the GNOME table) than flat-out 
reverted.

What do you think?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-02-17 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 18:41 bug#39648: Reverse my commits on GNOME meta-package Raghav Gururajan
2020-02-17 19:02 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-02-17 19:09   ` Raghav Gururajan
2020-02-17 19:19   ` Gábor Boskovits
2020-02-17 19:25     ` Raghav Gururajan
2020-02-22 17:08   ` bug#39646: " Ludovic Courtès
2020-02-23  1:19   ` Raghav Gururajan
2020-02-23 11:48     ` Ludovic Courtès

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=875zg56nq4.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=39648@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=me@tobias.gr \
    --cc=raghavgururajan@disroot.org \
    /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).