Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org, Stefano Sabatini <stefasab@gmail.com>
Subject: Re: [FFmpeg-devel] [REFUND-REQUEST] VDD23 Travel
Date: Sun, 1 Oct 2023 14:18:22 +0100
Message-ID: <7e53f8da-3043-e65d-c4d4-e67d26de8f13@gmail.com> (raw)
In-Reply-To: <ZRZsK47dujRsqnba@mariano>

On 9/29/2023 7:18 AM, Stefano Sabatini wrote:
> Once this is approved, follow instructions here to generate a refund request:
> https://www.spi-inc.org/treasurer/reimbursement-form/

One note: One step says to use the xe.com expensed calculator - however the
link provided is broken. Indeed the link on xe's own page (https://www.xe.com/tools/#convertertools)
is broke. Google yeilds https://www.xe.com/travel-expenses-calculator/table.shtml but
it is *also* broken - it cannot generate reports. So how am I suppose to do this?

This really highlights how depending on a third party service (Xe) can be problematic.

- Derek

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2023-10-01 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 13:17 Derek Buitenhuis
2023-09-29  6:18 ` Stefano Sabatini
2023-09-29 17:34   ` Michael Niedermayer
2023-10-01 13:18   ` Derek Buitenhuis [this message]
2023-10-05 22:46     ` Stefano Sabatini
2023-10-06 14:13       ` Derek Buitenhuis
2023-10-08  2:09 [FFmpeg-devel] [REFUND-REQUEST]] " Steven Liu
2023-10-10  6:08 ` Stefano Sabatini
2023-10-24  1:46   ` Steven Liu
2023-10-10 10:29 ` Michael Niedermayer
2023-10-21 12:10 [FFmpeg-devel] [REFUND-REQUEST] " Anton Khirnov
2023-10-23 20:42 ` Michael Niedermayer
2023-10-23 21:02   ` Stefano Sabatini

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=7e53f8da-3043-e65d-c4d4-e67d26de8f13@gmail.com \
    --to=derek.buitenhuis@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=stefasab@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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git