Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3] doc/html: Support texinfo 7.0
Date: Thu, 9 Nov 2023 00:27:46 +0100
Message-ID: <20231108232746.GT3543730@pb2> (raw)
In-Reply-To: <ZUwS5KJiroOGfIhW@mariano>


[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]

On Wed, Nov 08, 2023 at 11:59:48PM +0100, Stefano Sabatini wrote:
> On date Wednesday 2023-11-08 23:56:46 +0100, Stefano Sabatini wrote:
> > On date Wednesday 2023-11-08 16:53:27 +0000, Frank Plowman wrote:
> > > Patches attached.
> > > 
> > > Changes since v2: * Split changes to t2h.pm and bootstrap.min.css into
> > > separate commits. * Add justification for CSS changes to commit message.
> > 
> > Thanks, both applied.
> 
> For clarification, they were applied to master.
> 
> Where should they be backported? (not sure 6.1 branch was already
> created).

I just backported it locally to all branches between 3.4 and 6.1
3.4 to 4.4 needed 2 more patches :)

normally backports should be to all maintained branches (excluding anything
thats too hard and excluding anything where the risk of regressions exceeds
the gain)
I did it here as i want to make releases of 5.1/6.0 soonish

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin

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

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2023-11-08 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 15:57 [FFmpeg-devel] [PATCH v2] doc/t2h: " Frank Plowman
2023-11-07 20:38 ` epirat07
2023-11-07 21:44   ` Frank Plowman
2023-11-07 22:32     ` epirat07
2023-11-08  0:15       ` Stefano Sabatini
2023-11-08  8:03 ` [FFmpeg-devel] [PATCH v3] doc/html: " Frank Plowman
2023-11-08 16:53 ` Frank Plowman
2023-11-08 22:56   ` Stefano Sabatini
2023-11-08 22:59     ` Stefano Sabatini
2023-11-08 23:27       ` Michael Niedermayer [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=20231108232746.GT3543730@pb2 \
    --to=michael@niedermayer.cc \
    --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