From: Derrick Stolee <derrickstolee@github.com>
To: Victoria Dye via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Johannes.Schindelin@gmx.de, gitster@pobox.com,
Victoria Dye <vdye@github.com>
Subject: Re: [PATCH v2 0/2] scalar: prepare documentation for future work
Date: Fri, 15 Jul 2022 12:53:49 -0400 [thread overview]
Message-ID: <bb415e89-896d-b399-1e96-7ab1642ff3ec@github.com> (raw)
In-Reply-To: <pull.1275.v2.git.1657584367.gitgitgadget@gmail.com>
On 7/11/2022 8:06 PM, Victoria Dye via GitGitGadget wrote:
>
> Changes since V1
> ================
>
> * Moved 'contrib/scalar/technical/scalar.txt' to
> 'Documentation/technical/scalar.txt'.
> * Rephrased/removed references to Scalar being "built-in" to avoid
> confusion with the 'git ' built-ins.
> * Fixed line wrapping of bullet points in "Roadmap".
> * Removed the "[RFC]" tag.
Sorry I'm late to respond. I added a reply to the v1 discussion,
but this v2 looks good to me. I'm looking forward to seeing your
next steps.
Thanks!
-Stolee
prev parent reply other threads:[~2022-07-15 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 16:58 [PATCH 0/2] [RFC] scalar: prepare documentation for future work Victoria Dye via GitGitGadget
2022-06-29 16:58 ` [PATCH 1/2] scalar: reword command documentation to clarify purpose Victoria Dye via GitGitGadget
2022-06-29 16:58 ` [PATCH 2/2] scalar: convert README.md into a technical design doc Victoria Dye via GitGitGadget
2022-06-29 17:58 ` Derrick Stolee
2022-07-11 23:05 ` Victoria Dye
2022-07-15 16:52 ` Derrick Stolee
2022-06-29 17:41 ` [PATCH 0/2] [RFC] scalar: prepare documentation for future work Derrick Stolee
2022-06-29 21:50 ` Johannes Schindelin
2022-07-12 0:06 ` [PATCH v2 0/2] " Victoria Dye via GitGitGadget
2022-07-12 0:06 ` [PATCH v2 1/2] scalar: reword command documentation to clarify purpose Victoria Dye via GitGitGadget
2022-07-12 0:06 ` [PATCH v2 2/2] scalar: convert README.md into a technical design doc Victoria Dye via GitGitGadget
2022-07-15 16:53 ` Derrick Stolee [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=bb415e89-896d-b399-1e96-7ab1642ff3ec@github.com \
--to=derrickstolee@github.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=vdye@github.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).