Mark H Weaver (2015-08-22 20:31 +0300) wrote:
> Alex Kost writes:
>
>> From 55e67d4f3867f11a77b9a91d4c3c54599846cc83 Mon Sep 17 00:00:00 2001
>> From: Alex Kost
>> Date: Mon, 17 Aug 2015 21:44:40 +0300
>> Subject: [PATCH] gnu: magit: Update to 2.2.0.
>>
Alex Kost writes:
> From 55e67d4f3867f11a77b9a91d4c3c54599846cc83 Mon Sep 17 00:00:00 2001
> From: Alex Kost
> Date: Mon, 17 Aug 2015 21:44:40 +0300
> Subject: [PATCH] gnu: magit: Update to 2.2.0.
>
> * gnu/packages/emacs.scm (magit): Update to 2.2.0.
> [inp
Thompson, David (2015-08-17 22:38 +0300) wrote:
> The patch looks good to me. Just one question: Should we leave the
> magit 1.4 package around for awhile? Magit 2.0 is a pretty huge
> change. I don't have a preference, but figured I'd throw it out
> there.
Magit 1.4 is obsolete and "Magit 1 s
On Tue, Aug 18, 2015 at 3:19 AM, Alex Kost wrote:
> Thompson, David (2015-08-17 22:38 +0300) wrote:
>
>> The patch looks good to me. Just one question: Should we leave the
>> magit 1.4 package around for awhile? Magit 2.0 is a pretty huge
>> change. I don't have a preference, but figured I'd th
On Mon, Aug 17, 2015 at 2:56 PM, Alex Kost wrote:
> Thanks, Mark, for the hint about using (package-version emacs-dash) to
> define its elisp directory.
The patch looks good to me. Just one question: Should we leave the
magit 1.4 package around for awhile? Magit 2.0 is a pretty huge
change. I
Thanks, Mark, for the hint about using (package-version emacs-dash) to
define its elisp directory.
>From 55e67d4f3867f11a77b9a91d4c3c54599846cc83 Mon Sep 17 00:00:00 2001
From: Alex Kost
Date: Mon, 17 Aug 2015 21:44:40 +0300
Subject: [PATCH] gnu: magit: Update to 2.2.0.
* gnu/packages/emacs.