From: "Wang, Fei W" <fei.w.wang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: "Wang, Fei W" <fei.w.wang@intel.com> Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add myself to the general developers list Date: Sun, 7 Jul 2024 11:21:19 +0000 Message-ID: <PH0PR11MB5030235DA0847C04854A60EACDD92@PH0PR11MB5030.namprd11.prod.outlook.com> (raw) In-Reply-To: <20240630061742.576086-1-fei.w.wang@intel.com> > -----Original Message----- > From: Wang, Fei W <fei.w.wang@intel.com> > Sent: Sunday, June 30, 2024 2:18 PM > To: ffmpeg-devel@ffmpeg.org > Cc: Wang, Fei W <fei.w.wang@intel.com> > Subject: [FFmpeg-devel][PATCH] MAINTAINERS: add myself to the general > developers list > > From: Fei Wang <fei.w.wang@intel.com> > > Signed-off-by: Fei Wang <fei.w.wang@intel.com> > --- > It has been 4.5 years since my 1st patch to FFmpeg. During the past years, I > have fully understand the rules of a committer. Because sometimes, patch > send to community will be stay there without review or patch get reviewed > and approved but can't be get merged. So to make the work more efficient > and to contribute some of my help as a committer, I'd like to apply to get > write access. Thanks. Ping. Thanks. -- Fei > > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index a82fa58c69..d794e58163 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -514,6 +514,7 @@ Benjamin Larsson > Bobby Bingham > Daniel Verkamp > Derek Buitenhuis > +Fei Wang > Ganesh Ajjanagadde > Henrik Gramner > Ivan Uskov > -- > 2.34.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".
next prev parent reply other threads:[~2024-07-07 11:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-30 6:17 fei.w.wang-at-intel.com 2024-07-07 11:21 ` Wang, Fei W [this message] 2024-07-07 20:14 ` 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=PH0PR11MB5030235DA0847C04854A60EACDD92@PH0PR11MB5030.namprd11.prod.outlook.com \ --to=fei.w.wang-at-intel.com@ffmpeg.org \ --cc=fei.w.wang@intel.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