From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26284@debbugs.gnu.org, Vasile Dumitrascu <va511e@yahoo.com>
Subject: bug#26284: [PATCH] gnu: emacs-symon: Update to 20160630.
Date: Fri, 07 Apr 2017 20:26:54 +0300 [thread overview]
Message-ID: <87inmgxh5t.fsf@gmail.com> (raw)
In-Reply-To: <8737dv5f1l.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 30 Mar 2017 10:45:10 +0200")
Ludovic Courtès (2017-03-30 10:45 +0200) wrote:
> Hi Vasile,
>
> Vasile Dumitrascu <va511e@yahoo.com> skribis:
>
>> * gnu/packagages/emacs.scm (emacs-symon): Update to 20160630.
>> [source]: Use github instead of melpa.
>>
>> Version changed as previous version from melpa did not exist on github.
>> ---
>> gnu/packages/emacs.scm | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
>> index 4fe2ffa4d..d585f244a 100644
>> --- a/gnu/packages/emacs.scm
>> +++ b/gnu/packages/emacs.scm
>> @@ -1486,17 +1486,18 @@ strings.")
>> (define-public emacs-symon
>> (package
>> (name "emacs-symon")
>> - (version "20170224.33")
>> + (version "20160630")
>
> This looks like a downgrade, is it intended? :-)
>
> Is it that there was no “v20170224.33” tag on GitHub?
Yes, that's it, as Vasile answered. I think this downgrade is not a
problem since there were only 2 commits between these 2 versions (and
one of them is "Add .gitignore"). All in all, we'll have the same
version as MELPA-stable has, and the upstream can always be asked to add
a new tag. So I committed this patch, I hope you don't mind :-)
--
Alex
next prev parent reply other threads:[~2017-04-07 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 19:50 bug#26284: [PATCH] gnu: emacs-symon: Update to 20160630 Vasile Dumitrascu
2017-03-30 8:45 ` Ludovic Courtès
2017-03-30 9:34 ` Vasile Dumitrascu
2017-04-07 17:26 ` Alex Kost [this message]
2017-04-07 19:29 ` Ludovic Courtès
2017-04-07 17:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inmgxh5t.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=26284@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=va511e@yahoo.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.