unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 39648@debbugs.gnu.org
Subject: bug#39648: Reverse my commits on GNOME meta-package
Date: Mon, 17 Feb 2020 14:09:05 -0500	[thread overview]
Message-ID: <9f88fe4148c57c48b87206387daf8a7b9af84544.camel@disroot.org> (raw)
In-Reply-To: <875zg56nq4.fsf@nckx>

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


> 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?

I made a mistake of not reading comments of previous commits that were
done to gnome meta-package. Since we got lot of feedbacks regarding
gnome experience, I will re-conyemplate my plans for gnome, make the
changes, test it throughly and then re-commit later.

Also, this reverse should be smooth and does not break anything. It
just takes the GNOME meta-package back to the time before I started
making my commits to it.

Regards,
RG.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-02-17 19:10 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
2020-02-17 19:09   ` Raghav Gururajan [this message]
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=9f88fe4148c57c48b87206387daf8a7b9af84544.camel@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=39648@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).