From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: magit: Update to 2.2.1.
Date: Thu, 27 Aug 2015 18:20:52 +0300 [thread overview]
Message-ID: <87a8tcbvvv.fsf@gmail.com> (raw)
In-Reply-To: <877foh3x9w.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 27 Aug 2015 11:18:03 +0200")
Ludovic Courtès (2015-08-27 12:18 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> From ae74c836d38f3fb60ba0682c0b5010b81f6793c9 Mon Sep 17 00:00:00 2001
>> From: Alex Kost <alezost@gmail.com>
>> Date: Mon, 17 Aug 2015 21:44:40 +0300
>> Subject: [PATCH] gnu: magit: Update to 2.2.1.
>>
>> * gnu/packages/emacs.scm (magit): Update to 2.2.1.
>> [inputs]: Remove 'git:gui'.
>> [propagated-inputs]: Add 'dash', remove 'git-modes'.
>> [arguments]: Add PREFIX and DASH_DIR to 'make-flags'. Remove
>> 'configure', 'augment-load-path' and 'post-install' phases.
>
> LGTM.
>
> You should merge it with the magit-svn update at
> <https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00383.html> so
> we keep a working tool set.
>
> OK to push this combo!
Sure! I have pushed updates for all 3 git related emacs packages
(magit, magit-svn and git-modes), thanks.
So I wish people good luck with moving to Magit2 :-)
--
Alex
next prev parent reply other threads:[~2015-08-27 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 18:56 [PATCH] gnu: magit: Update to 2.2.0 Alex Kost
2015-08-17 19:38 ` Thompson, David
2015-08-18 7:19 ` Alex Kost
2015-08-18 12:11 ` Thompson, David
2015-08-22 17:31 ` Mark H Weaver
2015-08-22 20:48 ` Alex Kost
2015-08-25 19:04 ` [PATCH] gnu: magit: Update to 2.2.1 Alex Kost
2015-08-27 9:18 ` Ludovic Courtès
2015-08-27 15:20 ` Alex Kost [this message]
2015-08-29 14:39 ` Magit 2 troubleshooting Ludovic Courtès
2015-08-29 22:19 ` Alex Kost
2015-08-29 22:37 ` Alex Kost
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=87a8tcbvvv.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).