Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: AVX512-capable laptop
Date: Thu, 18 Jan 2024 10:54:51 +0100
Message-ID: <CAPYw7P6BkRQ4iuy_x+nPBPhMX1fpdTre3NXwaHX=jrACkytQFg@mail.gmail.com> (raw)
In-Reply-To: <CAK+ULv5P3fysOt-sm_JUvSZg1aymxebcNytmbaQk2UsRw9KE6Q@mail.gmail.com>

On Thu, Jan 18, 2024 at 10:53 AM Kieran Kunhya <kierank@obe.tv> wrote:

> > >> It's a high-spec 4-core machine with 16Gb of RAM, and still very
> > >> usable these days, but it'll take around 400 dollars to repair,
> > >> as a new original screen is expensive (290), battery isn't cheap (60),
> > >> and parts are in general in demand as it's out of support by now.
> > >>
> > >
> > > well i would certainly support ffmpeg-SPI paying for these parts
> > > if it helps you.
> > >
> >
> > Right, thanks. But would the main two currently objecting agree?
> > I don't think they monitor this thread anymore, but their objections
> stand.
> >
>
> I object to buying parts that may not work, or the install may not go well
> (I tried repairing my old XPS and it was not simple and I broke the
> screen).
> I don't think "worth a try" is fair to FFmpeg donors.
>

Just kill the project and take all the money already.


>
> Kieran
> _______________________________________________
> 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".
>
_______________________________________________
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".

  reply	other threads:[~2024-01-18  9:55 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  0:56 Lynne
2024-01-03  1:22 ` James Almer
2024-01-03  3:04   ` Lynne
2024-01-03 13:46     ` Michael Niedermayer
2024-01-05 17:36     ` James Almer
     [not found]   ` <NnCGm7x--3-9@lynne.ee-NnCGqE2----9>
2024-01-03  3:30     ` Lynne
2024-01-03  5:28       ` Kieran Kunhya
     [not found]     ` <NnCMnsG--3-9@lynne.ee-NnCMrYP--J-9>
2024-01-09 18:57       ` Lynne
     [not found]       ` <Nnj2jS_--3-9@lynne.ee-Nnj_bOo--3-9>
2024-01-14 17:23         ` Lynne
2024-01-15  8:57           ` Kieran Kunhya
2024-01-15 14:06             ` Paul B Mahol
2024-01-15 16:01               ` Rémi Denis-Courmont
2024-01-15 16:07                 ` Paul B Mahol
2024-01-15 16:10                   ` Nicolas George
2024-01-15 17:30                     ` Michael Niedermayer
2024-01-15 14:59             ` Lynne
2024-01-15 16:01               ` Rémi Denis-Courmont
2024-01-15 17:36                 ` Lynne
2024-01-15 18:50                   ` Kieran Kunhya
2024-01-15 21:47                     ` Michael Niedermayer
2024-01-16  0:03                     ` Lynne
2024-01-16 10:05                       ` Kieran Kunhya
2024-01-16 11:50                         ` Paul B Mahol
2024-01-16 11:54                           ` Kieran Kunhya
2024-01-16 14:59                         ` Lynne
2024-01-17 13:37                           ` Michael Niedermayer
2024-01-17 15:39                             ` Lynne
2024-01-18  3:28                               ` Michael Niedermayer
2024-01-18  4:07                                 ` Lynne
2024-01-18  8:42                                   ` Steve Williams via ffmpeg-devel
2024-01-18  9:52                                   ` Kieran Kunhya
2024-01-18  9:54                                     ` Paul B Mahol [this message]
2024-01-18  9:57                                       ` Kieran Kunhya
2024-01-18 17:19                                         ` Paul B Mahol
2024-01-18 22:59                                         ` Michael Niedermayer
     [not found]                                   ` <25e0763a-4b07-4328-ba93-354d23c8e591@advance-software.com-NoQj7Fn----9>
2024-01-18 15:37                                     ` Lynne
     [not found]                                 ` <NoPk9Ny--3-9@lynne.ee-NoPkD07----9>
2024-01-18 12:32                                   ` Lynne
2024-01-05 17:24 ` Rémi Denis-Courmont
2024-01-05 17:31   ` Kieran Kunhya
2024-01-06 10:38   ` Lynne
2024-01-06 11:09     ` Rémi Denis-Courmont
2024-01-06 16:13       ` Lynne
2024-01-06 17:57         ` Rémi Denis-Courmont
2024-01-06 18:01           ` Lynne
     [not found]       ` <NnUYG5V--3-9@lynne.ee-NnUYKEn----9>
2024-01-06 16:21         ` Lynne
2024-01-06 18:11           ` Rémi Denis-Courmont
2024-01-06 18:26             ` Michael Niedermayer
2024-01-06 20:15               ` Rémi Denis-Courmont
2024-01-06 21:06                 ` Lynne
2024-01-06 23:36                   ` Kieran Kunhya
2024-01-07  0:00                     ` Lynne
2024-01-07  0:40                       ` Kieran Kunhya
2024-01-07  1:55                         ` Lynne
2024-01-07  3:14                           ` Kieran Kunhya
2024-01-06 17:59       ` Michael Niedermayer
2024-01-06 18:21         ` Rémi Denis-Courmont
2024-01-06 18:28           ` Lynne
2024-01-06 17:42 ` Michael Niedermayer
2024-01-10  2:31   ` Michael Niedermayer
2024-01-10  2:56     ` Lynne
2024-01-10 13:06       ` Paul B Mahol
2024-01-10 17:58       ` Michael Niedermayer

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='CAPYw7P6BkRQ4iuy_x+nPBPhMX1fpdTre3NXwaHX=jrACkytQFg@mail.gmail.com' \
    --to=onemda@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.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

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