From: Vinayak Dev <vinayakdev.sci@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: add necessary headers to Documentation/MFOW.txt
Date: Wed, 5 Jul 2023 12:46:31 +0530 [thread overview]
Message-ID: <CADE8Napg5ps9NywJS_P6wGnGVVCv9eqvEZXKVbZ-wWGZbjzHOQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqilay3mzg.fsf@gitster.g>
On Wed, 5 Jul 2023 at 11:42, Junio C Hamano <gitster@pobox.com> wrote:
> That is OK. So the other one turned out to be a work-in-progress,
> and this is the final version, right?
Yes, I included all the files that did not have any mentions in the tutorial.
This should work perfectly fine. But the repository to which the tutorial points
still contains stale code. It might require a re-write, so I will cc Emily too.
> Thanks for working on this. Will queue.
Thanks a lot!
Have a good day!
Vinayak
prev parent reply other threads:[~2023-07-05 7:16 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
2023-07-05 7:16 ` Vinayak Dev [this message]
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=CADE8Napg5ps9NywJS_P6wGnGVVCv9eqvEZXKVbZ-wWGZbjzHOQ@mail.gmail.com \
--to=vinayakdev.sci@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nasamuffin@google.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).