Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] When to add 'Reviewed-by: xxx' in commit messages
Date: Mon, 26 May 2025 23:07:40 +0000
Message-ID: <DM8P223MB0365208839348092F00BC121BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB036583EEE5DD0072AF3DD0EEBA8C2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Samstag, 3. Mai 2025 11:32
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: [FFmpeg-devel] When to add 'Reviewed-by: xxx' in commit messages
> 
> Hello everybody,
> 
> I have an organizational question that I cannot quite figure out how to do it
> right:
> 
> Whether and when to add 'Reviewed-by:  xxx' to a commit message?
> 
> Specific example: The “execution graph printing” patchset:
> 
> Andreas had reviewed the patchset initially. I addressed the mentioned
> issues. Is that the point to add 'Reviewed-by:’ already? And what about
> the commits without comments? Should I assume them to be reviewed
> as well? And how about later changes, do they invalidate it?
> 
> From Stefano, I believe that he didn’t review the last two commits (due
> to being outside of the text formatting scope, I suppose). I added him
> as “reviewed by” only to those where he said “should be ok” or similar.
> Andreas didn’t say anything like that, yet I’m sure that he has carefully
> looked over everything.
> 
> It might not be a big thing after all, but I don't want to be unjust to
> anybody and I'm unsure how to handle this, because I can imagine that
> someone might either say "Hey, why is he mentioning me, that's not the
> version that I have reviewed!" but also "Why doesn't he mention me, I've
> reviewed the whole thing in detail?".
> That's the circle by which I got trapped at the moment. 😉
> 
> I'd be glad if somebody could provide me some guidance in this regard.
> 
> Thanks a lot,
> sw
> _______________________________________________

Hello everybody,
 
recently, I've been criticized for this message on IRC as follows:

"softworkz: last month you even had to publicly ask on the mailing list 
about a policy which pretty much everyone understood"


So - what does this mean to express? That it would be an indication of 
incompetence when somebody is asking others for advice on something one
doesn't know?

What _I_ consider as a sign of incompetence is just the opposite: 
Pretending to know everything without knowing, and being afraid of 
asking questions as that might shed a bad light on oneself.

When I have a question on something that I do not know, then I ask that
question, no matter what anybody might think about it.
Because - at the end of the day - I'll be the one who knows the answer
and all those who were just pretending to know it - won't 
(unless public like here).

And anyway, where are we - that asking for advice would be a bad thing?

---

In this regard, I still don't know the answer. It's not about the basic
principle of procedure but goes into some quite specific whereabouts
where I'm not sure how exactly it is supposed to be done.


Thanks a lot for any advice or guidance.
sw

_______________________________________________
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:[~2025-05-26 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-03  9:32 softworkz .
2025-05-26 23:07 ` softworkz . [this message]
2025-05-27  9:28 ` Marvin Scholz
2025-05-27 19:58   ` softworkz .

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=DM8P223MB0365208839348092F00BC121BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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