Git development
 help / color / mirror / Atom feed
From: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Cc: <git@vger.kernel.org>, <jltobler@gmail.com>, <ps@pks.im>
Subject: Re: [PATCH v3 1/1] repo: add filtering options to "repo structure"
Date: Sat, 10 Oct 2026 10:31:31 -0400	[thread overview]
Message-ID: <DM18BTUM3WZH.3S2G5JAJ93AXC@fastmail.com> (raw)
In-Reply-To: <xmqqse2elg8j.fsf@gitster.g>

On Fri Oct 9, 2026 at 5:24 PM EDT, Junio C Hamano wrote:
> "Mark C. Chu-Carroll" <markchucarroll@fastmail.com> writes:
>
>> diff --git a/revision.c b/revision.c
>> index ee1df92d1d..79d44b58b5 100644
>> --- a/revision.c
>> +++ b/revision.c
>> @@ -2837,7 +2837,7 @@ static int handle_revision_pseudo_opt(struct rev_info *revs,
>>  	 * NOTE!
>>  	 *
>>  	 * Commands like "git shortlog" will not accept the options below
>> -	 * unless parse_revision_opt queues them (as opposed to erroring
>> +	 * unless parse_revision_op	t queues them (as opposed to erroring
>>  	 * out).
>>  	 *
>>  	 * When implementing your new pseudo-option, remember to
>
> What is this change about?
>
>> diff --git a/revision.h b/revision.h
>> index e5dabd18ce..63135c5f88 100644
>> --- a/revision.h
>> +++ b/revision.h
>> @@ -125,7 +125,7 @@ struct topo_walk_info;
>>  
>>  struct rev_info {
>>  	/*
>> -	 * Work queue of commits, stored as either a linked list or a
>> +~	 * Work queue of commits, stored as either a linked list or a
>>  	 * priority queue, but never both at the same time.
>>  	 * rev_info_commit_list_to_queue() converts list to queue.
>>  	 */
>
> Ditto.
>
> Everybody makes mistakes during their editing, and occasionally fat
> thumb hits unintended keys while the cursor is in an area one is not
> editing at all.  Mistakes happen and that is perfectly OK.
>
> But a hunk like this one in a submitted patch is a clear sign that
> even the author is not reading what they are sending out.  And this
> patch, among its 16 hunks, two are such hunks that was never
> proofread.
>
> Quite honestly, it is beyond me how anybody would expect others to
> seriously take their time to review such a patch.

I'm really sorry - I honestly don't know how this slipped through.
I went through _so_ many revisions of this patch trying to make sure
that everything was correct. I caught this mistake and fixed it, but
fat-fingered and sent the wrong version. I'm really annoyed at myself -
I've put a lot of time into this change. I got the hard parts right,
and went and found a way to screw up the simple part - sending the
right $^#&@! version.




-- 
Mark Craig Chu-Carroll (@MarkChuCarroll at gitlab)
*** Software Tools/Math Geek - Software Engineer at Gitlab
*** Work Email: mcarroll@gitlab.com / markchucarroll@fastmail.com
*** Personal Blog: http://goodmath.org/blog / Personal email: markcc@gmail.com


  reply	other threads:[~2026-10-10 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 16:45 [PATCH 0/1] repo: add filtering options to "repo structure" Mark C. Chu-Carroll
2026-09-24 16:45 ` [PATCH 1/1] " Mark C. Chu-Carroll
2026-09-30 16:28   ` Patrick Steinhardt
2026-10-05 18:52     ` Mark C. Chu-Carroll
2026-10-05 17:40   ` [PATCH v2 0/1] " Mark C. Chu-Carroll
2026-10-05 17:40     ` [PATCH v2 1/1] " Mark C. Chu-Carroll
2026-10-06  5:51       ` Patrick Steinhardt
2026-10-08 15:46         ` Kaartic Sivaraam
2026-10-09 15:49           ` Mark C. Chu-Carroll
2026-10-09 18:09   ` [PATCH v3 0/1] repo: add revision " Mark C. Chu-Carroll
2026-10-09 18:09     ` [PATCH v3 1/1] repo: add " Mark C. Chu-Carroll
2026-10-09 21:24       ` Junio C Hamano
2026-10-10 14:31         ` Mark C. Chu-Carroll [this message]
2026-10-10 15:05   ` [PATCH v4 0/1] repo: add revision " Mark C. Chu-Carroll
2026-10-10 15:05     ` [PATCH v4 1/1] repo: add " Mark C. Chu-Carroll

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=DM18BTUM3WZH.3S2G5JAJ93AXC@fastmail.com \
    --to=markchucarroll@fastmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@gmail.com \
    --cc=ps@pks.im \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox