From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43292@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#43292] [PATCH] gnu: emacs-org-contrib: Fix hash for version 20200907.
Date: Wed, 09 Sep 2020 15:23:31 +0200 [thread overview]
Message-ID: <87sgbrm6cs.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJ3okZ3aMQC95ybmCnV8W914aQ5PrO4b_O4b9k8mwh2dD2JC7g@mail.gmail.com> (zimoun's message of "Wed, 9 Sep 2020 14:03:02 +0200")
Hello,
zimoun <zimon.toutoune@gmail.com> writes:
> On Wed, 9 Sep 2020 at 13:49, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
>> On 2020-09-09 13:35, zimoun wrote:
>> > * gnu/packages/emacs-xyz.scm (emacs-org-contrib): Fix hash.
>>
>> Thanks! It's probably irrational, but in-place updates always tingle my
>> paranoia. What did they change? Why?
>
> I do not understand either.
> Maybe Nicolas could tell us more about this in-place update?
Package is updated automatically either every Monday, provided there is
at least a pending commits since last update, or whenever a new Org is
released.
When new Org is released on a Monday, two updates happen the same day,
and therefore share the same version. It is unfortunate, but quite rare
in practice, and when the day is over, the source file cannot change
anymore.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-09-09 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 11:35 [bug#43292] [PATCH] gnu: emacs-org-contrib: Fix hash for version 20200907 zimoun
2020-09-09 11:50 ` Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 12:03 ` zimoun
2020-09-09 13:23 ` Nicolas Goaziou [this message]
2020-09-09 13:35 ` Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 14:05 ` Nicolas Goaziou
2020-09-09 14:00 ` zimoun
2020-09-09 12:33 ` bug#43292: " Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 12:56 ` [bug#43292] " zimoun
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=87sgbrm6cs.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=43292@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=zimon.toutoune@gmail.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.