From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in Date: Wed, 5 Jan 2022 16:25:38 +0100 Message-ID: <AM7PR03MB6660315F93C1E5D50D62EF408F4B9@AM7PR03MB6660.eurprd03.prod.outlook.com> (raw) In-Reply-To: <20220104200626.21573-1-michael@niedermayer.cc> Michael Niedermayer: > maintainer part inspired by IRC comments by lynne > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > doc/developer.texi | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/doc/developer.texi b/doc/developer.texi > index addee0d8263..eae3ade48a7 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -683,6 +683,10 @@ are notoriously left unchecked, which is a serious problem. > @item > Test your code with valgrind and or Address Sanitizer to ensure it's free > of leaks, out of array accesses, etc. > + > +@item > +Changes to 2 libs which change both versions should be in 2 seperate patches. ^ ^ maybe spell this out a (I presume that the pre- and post-release version bump patches are supposed to be exempt from this?) > +Non cosmetic changes to @file{MAINTAINERS} should not be in a patch with other changes. > @end enumerate > > @chapter Patch review process > _______________________________________________ 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".
prev parent reply other threads:[~2022-01-05 15:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 20:06 Michael Niedermayer 2022-01-05 2:42 ` Lynne 2022-01-05 15:25 ` Andreas Rheinhardt [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=AM7PR03MB6660315F93C1E5D50D62EF408F4B9@AM7PR03MB6660.eurprd03.prod.outlook.com \ --to=andreas.rheinhardt@outlook.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