all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Hamelink <me@johnhame.link>
To: 54939@debbugs.gnu.org
Subject: bug#54939: 29.0.50; icalendar cannot infer the DTEND from DTSTART + DURATION
Date: Mon, 25 Apr 2022 11:50:55 +0100	[thread overview]
Message-ID: <87bkwptone.fsf@johnhame.link> (raw)
In-Reply-To: <87o80yrwk2.fsf@johnhame.link>


[-- Attachment #1.1.1: Type: text/plain, Size: 883 bytes --]

John Hamelink <me@johnhame.link> writes:

> OK, in that case I'll try to fix the function responsibly, and I'll
> try to find all usages of the function and change them accordingly.

Just wanted to send a holding-pattern update: I'm currently very busy
in the run-up to a local election on the 5th May here in Scotland, so
I probably won't be able to come back to this for a few weeks.

> I've also sent my side of the copy-assignment paperwork back, and I've
> asked my employer to sign their side. I already have a clause in my
> contract which says something similar to what is said in the
> disclaimer, so things should move quickly on that front.

I haven't heard back from FSF on this - which is fine since I'm so
busy - but FWIW I will try to be as responsive as I can if any further
requirements are discovered before the copyright assignment process
has completed.

Best
JH

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

      reply	other threads:[~2022-04-25 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 13:44 bug#54939: 29.0.50; icalendar cannot infer the DTEND from DTSTART + DURATION John Hamelink
2022-04-14 14:53 ` Lars Ingebrigtsen
2022-04-14 19:09   ` John Hamelink
2022-04-15  9:39     ` John Hamelink
2022-04-17 18:00 ` Paul Eggert
2022-04-18 19:50   ` John Hamelink
2022-04-25 10:50     ` John Hamelink [this message]

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=87bkwptone.fsf@johnhame.link \
    --to=me@johnhame.link \
    --cc=54939@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.