* [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in
@ 2022-01-04 20:06 Michael Niedermayer
2022-01-05 2:42 ` Lynne
2022-01-05 15:25 ` Andreas Rheinhardt
0 siblings, 2 replies; 3+ messages in thread
From: Michael Niedermayer @ 2022-01-04 20:06 UTC (permalink / raw)
To: FFmpeg development discussions and patches
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.
+Non cosmetic changes to @file{MAINTAINERS} should not be in a patch with other changes.
@end enumerate
@chapter Patch review process
--
2.17.1
_______________________________________________
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".
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in
2022-01-04 20:06 [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in Michael Niedermayer
@ 2022-01-05 2:42 ` Lynne
2022-01-05 15:25 ` Andreas Rheinhardt
1 sibling, 0 replies; 3+ messages in thread
From: Lynne @ 2022-01-05 2:42 UTC (permalink / raw)
To: FFmpeg development discussions and patches
4 Jan 2022, 21:06 by michael@niedermayer.cc:
> 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.
> +Non cosmetic changes to @file{MAINTAINERS} should not be in a patch with other changes.
> @end enumerate
>
LGTM
_______________________________________________
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".
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in
2022-01-04 20:06 [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in Michael Niedermayer
2022-01-05 2:42 ` Lynne
@ 2022-01-05 15:25 ` Andreas Rheinhardt
1 sibling, 0 replies; 3+ messages in thread
From: Andreas Rheinhardt @ 2022-01-05 15:25 UTC (permalink / raw)
To: ffmpeg-devel
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".
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-05 15:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-04 20:06 [FFmpeg-devel] [PATCH] doc/developer: patches should not cross libs or mix MAINTAINER changes in Michael Niedermayer
2022-01-05 2:42 ` Lynne
2022-01-05 15:25 ` Andreas Rheinhardt
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