Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] git email hook
Date: Sat, 15 Jul 2023 20:34:10 +0200
Message-ID: <ZLLmokq84zA6cvG+@phare.normalesup.org> (raw)
In-Reply-To: <20230714182706.GO1093384@pb2>


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

Michael Niedermayer (12023-07-14):
> I today added and tested git-multimail to git.ffmpeg.org as our git mail
> sending script is old and unmaintained
> 
> I intend to use libavradio for testing it, this will result in
> different looking mails for avradio. (probably on the next push in a day or 2)
> If that goes well i intend to switch ffmpeg-web and all repositories
> that are on git.ffmpeg.org over to it too. But its easy to leave some
> on the old script if people prefer.
> I hope though the new will produce nicer mails.
> (this is unrelated to git master for which videolan is doing the git mail)
> 
> No ill sideeffects are expected but unexpected things are always possible.

Hi.

Can the "branch master updated:" be removed? We only work on master
anyway, it takes up space and the interesting part of the commit subject
gets truncated.

Regards,

-- 
  Nicolas George

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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-07-15 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 18:27 Michael Niedermayer
2023-07-15 18:34 ` Nicolas George [this message]
2023-07-15 20:09   ` Michael Niedermayer
2023-07-16  9:51     ` Nicolas George
2023-07-17 23:37       ` 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=ZLLmokq84zA6cvG+@phare.normalesup.org \
    --to=george@nsup.org \
    --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