From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Better {} style rule
Date: Fri, 28 Feb 2025 04:22:28 +0100
Message-ID: <20250228032228.GS4991@pb2> (raw)
In-Reply-To: <1F96354D-B189-4A6D-82FD-81DD1C0016B1@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2665 bytes --]
On Fri, Feb 28, 2025 at 12:25:43AM +0100, epirat07@gmail.com wrote:
>
>
> On 28 Feb 2025, at 0:14, Michael Niedermayer wrote:
>
> > Hi
> >
> > On Thu, Feb 27, 2025 at 11:46:54PM +0100, epirat07@gmail.com wrote:
> >> On 27 Feb 2025, at 2:10, Michael Niedermayer wrote:
> >>
> >>> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> >>> ---
> >>> doc/developer.texi | 11 +++++------
> >>> 1 file changed, 5 insertions(+), 6 deletions(-)
> >>>
> >>> diff --git a/doc/developer.texi b/doc/developer.texi
> >>> index a1bfe180c9b..6a753f99da6 100644
> >>> --- a/doc/developer.texi
> >>> +++ b/doc/developer.texi
> >>> @@ -179,18 +179,17 @@ int fields = ilace ? 2 : 1;
> >>> @end example
> >>>
> >>> @item
> >>> -No braces around single-line blocks:
> >>> +No braces around single-line blocks, unless they are followed by an else (to keep future patches cleaner)
> >>>
> >>
> >> I agree with this, however people in the past pointed it out when new code did this, IIRC.
> >
> > yes, i know, ive seen it in both directions for this one.
> >
> >
> >>
> >> So if we merge this, people should stop flagging this in reviews, else its frustrating
> >> for new contributors following the documentation and then getting contradicting reviews.
> >
> > I think as long as its in a style guide, the author of a patch can easily
> > point the reviewer to the guide and that should resolve it immedeatly
> >
> > will apply
> >
>
> Sounds good.
>
> Can you maybe check the styling issue at some point?
> I had updated the CSS and locally I get the right classes assigned to the
> codeblocks and the CSS styling them to hint which of them are good and which
> bad examples.
>
> But on the website deployed version its not working.
there seem to be 2 style.min.css
one in ffmpeg and one generated by Makefile in ffmpeg-web
but only one on the website, this may be slightly suboptimal
ive simply copied the one from ffmpeg over on the server now, backup in
style.min.css.bak2 if it breaks something and timo wants to undo
also that change, did change the look of the frontpage, we have a bigger
download button now and some empty space
between entries in "October 30th, 2016, Results: Summer Of Code 2016."
some html/css person, should look at this i think.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary, page 1
"Used only once" - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."
[-- 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".
next prev parent reply other threads:[~2025-02-28 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 1:10 Michael Niedermayer
2025-02-27 22:46 ` epirat07
2025-02-27 22:53 ` Vittorio Giovara
2025-02-27 22:57 ` James Almer
2025-02-28 0:40 ` Devin Heitmueller
2025-02-28 0:58 ` Michael Niedermayer
2025-02-28 7:53 ` Nicolas George
2025-02-28 10:13 ` Marvin S.
2025-02-28 14:07 ` Devin Heitmueller
2025-02-28 14:16 ` Nicolas George
2025-02-28 14:21 ` martin schitter
2025-02-28 15:09 ` Nicolas George
2025-02-28 15:13 ` Vittorio Giovara
2025-02-28 1:11 ` Soft Works
2025-02-27 23:14 ` Michael Niedermayer
2025-02-27 23:25 ` epirat07
2025-02-28 3:22 ` Michael Niedermayer [this message]
2025-02-28 2:25 ` Lynne
2025-02-28 2:33 ` Michael Niedermayer
2025-02-28 12:24 ` Lynne
2025-02-28 13:44 ` Vittorio Giovara
2025-02-28 15:12 ` 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=20250228032228.GS4991@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