From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] MyFirstContribution: refrain from self-iterating too much
Date: Sun, 22 Jan 2023 09:14:42 -0800 [thread overview]
Message-ID: <xmqqsfg2qynx.fsf@gitster.g> (raw)
In-Reply-To: <xmqqcz76tv6d.fsf@gitster.g> (Junio C. Hamano's message of "Sun, 22 Jan 2023 08:01:46 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> Or:
>> Re-reading my own stuff, I think that things could have been done
>> in a way like this....
>> Lets wait for more comments before I send out a new version.
>
> Again, very good.
The latter one (different course) needs spearate treatment from the
former (typofix). Small corrections without changing course is
better communicated with "will fix when I reroll" while a drastic
change should warn the readers not to waste their time on the
premature initial version, i.e. "I came up with a drastically
different and better idea; please ignore the one I just posted and
wait for an updated one".
I'll sleep on what I rewrote to see if I or other people find better
phrasing.
Thanks.
next prev parent reply other threads:[~2023-01-22 17:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 1:51 [PATCH] MyFirstContribution: refrain from self-iterating too much Junio C Hamano
2023-01-22 7:11 ` Torsten Bögershausen
2023-01-22 16:01 ` Junio C Hamano
2023-01-22 17:14 ` Junio C Hamano [this message]
2023-01-23 4:18 ` [PATCH v2] " Junio C Hamano
2023-01-23 17:58 ` Torsten Bögershausen
2023-07-19 17:04 ` [PATCH v3] " Junio C Hamano
2023-07-27 23:14 ` Linus Arver
2023-07-28 0:25 ` Junio C Hamano
2023-07-28 0:43 ` [PATCH v4] " Junio C Hamano
2023-07-28 2:07 ` Jacob Abel
2023-07-28 5:10 ` Junio C Hamano
2023-07-28 15:42 ` Re* " Junio C Hamano
2023-07-29 2:12 ` Jacob Abel
2023-07-31 15:25 ` Junio C Hamano
2023-07-28 2:08 ` Linus Arver
2023-07-28 5:10 ` Junio C Hamano
2023-07-28 21:21 ` Torsten Bögershausen
2023-07-28 23:00 ` Junio C Hamano
2023-01-23 1:47 ` [PATCH] " Sean Allred
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsfg2qynx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).