From: Junio C Hamano <gitster@pobox.com>
To: Vinayak Dev <vinayakdev.sci@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: add necessary headers to Documentation/MFOW.txt
Date: Tue, 04 Jul 2023 23:12:51 -0700 [thread overview]
Message-ID: <xmqqilay3mzg.fsf@gitster.g> (raw)
In-Reply-To: <20230702151457.3227-1-vinayakdev.sci@gmail.com> (Vinayak Dev's message of "Sun, 2 Jul 2023 20:44:57 +0530")
Vinayak Dev <vinayakdev.sci@gmail.com> writes:
> I sent a patch to the mailing list previously, but today I noticed that
> the CI builds for the branch on my fork were failing. I turns out that
> the tutorial required addition of more files than I had noticed.
> I am really, really sorry for this mistake, but I am sure that the tutorial
> is fixed now. The CI builds now pass perfectly.
That is OK. So the other one turned out to be a work-in-progress,
and this is the final version, right?
Thanks for working on this. Will queue.
next prev parent reply other threads:[~2023-07-05 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 15:14 [PATCH] docs: add necessary headers to Documentation/MFOW.txt Vinayak Dev
2023-07-05 6:12 ` Junio C Hamano [this message]
2023-07-05 7:16 ` Vinayak Dev
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=xmqqilay3mzg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vinayakdev.sci@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).