Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Poorva <2003gaikarpoorva@gmail.com>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	Thilo Borgmann <thilo.borgmann@mail.de>,
	 Cosmin Stejerean <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] Fixes #10509
Date: Wed, 1 May 2024 15:20:35 +0530
Message-ID: <CAJdhrgnJ_G8f-J3-TS-VdSqBKhygKyik64638X7U5p5RZY5yYg@mail.gmail.com> (raw)
In-Reply-To: <d258bd41-22a6-a7dc-229d-5f8225b5c8e0@passwd.hu>

On Fri, Apr 5, 2024 at 2:08 AM Marton Balint <cus@passwd.hu> wrote:
>
>
>
> On Mon, 1 Apr 2024, Poorva wrote:
>
> >>
> >>
> >>
> > On Sun, Mar 31, 2024 at 8:35 PM Marton Balint <cus@passwd.hu> wrote:
> >
> >>
> >>
> >> On Fri, 29 Mar 2024, Poorva wrote:
> >>
> >>>>
> >>>
> >>> On Tue, Mar 26, 2024 at 2:36 AM Poorva <2003gaikarpoorva@gmail.com>
> >> wrote:
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> Thank you for your feedback on the Git patch I submitted for review.
> >>>> I have rectified the problem by adding the necessary changes .
> >>>> The updated patch file is attached for your review.
> >>>>>
> >>>>>
> >>> I wanted to follow up on the patch titled
> >>> "v3-0001-avfilter-f_select.c - Add Support for IW and IH" that I
> >>> submitted earlier and provide an update based on the feedback
> >>> received.
> >>>
> >>> In response to your suggestion about the switch block, I have
> >>> integrated the changes into the existing switch block for
> >>> AVMEDIA_TYPE_VIDEO. Additionally, I have removed an unnecessary new
> >>> line that was added at the end of the file.
> >>>
> >>> Despite these modifications, I have not received any further feedback
> >>> or comments on the patch. Therefore, I kindly request the community to
> >>> review the updated patch attached to this email.
> >>
> >> [..]
> >>
> >>> @@ -371,6 +383,7 @@ FF_ENABLE_DEPRECATION_WARNINGS
> >>>          break;
> >>>      }
> >>>
> >>> +
> >>>      select->select = res = av_expr_eval(select->expr,
> >> select->var_values, NULL);
> >>>      av_log(inlink->dst, AV_LOG_DEBUG,
> >>>             "n:%f pts:%f t:%f key:%d",
> >>> @@ -545,4 +558,4 @@ const AVFilter ff_vf_select = {
> >>>      FILTER_QUERY_FUNC(query_formats),
> >>>      .flags         = AVFILTER_FLAG_DYNAMIC_OUTPUTS |
> >> AVFILTER_FLAG_METADATA_ONLY,
> >>>  };
> >>> -#endif /* CONFIG_SELECT_FILTER */
> >>> +#endif /* CONFIG_SELECT_FILTER */
> >>> \ No newline at end of file
> >>> --
> >>> 2.43.0.windows.1
> >>>
> >>
> >> These two whitespace changes are still unnecessary. Please check your
> >> patch before sending.
> >>
> >> I did remove all the unnecessary whitespaces ,rest which are present are
> > to keep the code style .
> > Patch is attached to this email.
>
> No, the last hunk still removes a newline.
Sir, as far as I know git does that automatically.
>
> Regards,
> Marton
> _______________________________________________
> 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".
_______________________________________________
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:[~2024-05-01  9:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 20:49 Poorva
2024-03-10 19:40 ` Leo Izen
2024-03-16 18:47   ` Poorva
2024-03-16 18:56     ` Marton Balint
2024-03-18 17:04       ` Poorva
2024-03-24 14:28         ` Poorva
2024-03-24 20:34           ` Marton Balint
2024-03-25 21:06             ` Poorva
2024-03-28 19:34               ` Poorva
2024-03-31 15:05                 ` Marton Balint
2024-04-01 14:37                   ` Poorva
2024-04-04 20:38                     ` Marton Balint
2024-05-01  9:50                       ` Poorva [this message]
2024-05-07 22:04                         ` Marton Balint

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=CAJdhrgnJ_G8f-J3-TS-VdSqBKhygKyik64638X7U5p5RZY5yYg@mail.gmail.com \
    --to=2003gaikarpoorva@gmail.com \
    --cc=cosmin@cosmin.at \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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