From: Stefan Beller <sbeller@google.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git <git@vger.kernel.org>,
Jonathan Tan <jonathantanmy@google.com>,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH] partial-clone: render design doc using asciidoc
Date: Tue, 14 Aug 2018 16:00:55 -0700 [thread overview]
Message-ID: <CAGZ79kYbmTXXwWO6Sy5ytOLS6=p=9gMzgbjdrSbJPkkQqsyJTA@mail.gmail.com> (raw)
In-Reply-To: <20180814222846.GG142615@aiede.svl.corp.google.com>
On Tue, Aug 14, 2018 at 3:28 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
>
> Rendered documentation can be easier to read than raw text because
> headings and emphasized phrases stand out. Add the missing markup and
> Makefile rule required to render this design document using asciidoc.
>
> Tested by running
>
> make -C Documentation technical/partial-clone.html
>
> and viewing the output in a browser.
>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> ---
> Today I noticed that this document wasn't available at
> https://www.kernel.org/pub/software/scm/git/docs/technical/partial-clone.html,
> so I wrote this patch.
>
> Thoughts of all kinds welcome, as always.
yay! Thanks for writing it!
...
> repack in GC has been updated to not touch promisor
> packfiles at all, and to only repack other objects.
We'd need to adapt this documentation in Jonathans series?
> -[0] https://bugs.chromium.org/p/git/issues/detail?id=2
> - Chromium work item for: Partial Clone
> +[0] https://crbug.com/git/2
> + Bug#2: Partial Clone
This is more than a formatting fix (I did not quite check the rest,
but this stood out), but some change to the actual content?
next prev parent reply other threads:[~2018-08-14 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 22:28 [PATCH] partial-clone: render design doc using asciidoc Jonathan Nieder
2018-08-14 23:00 ` Stefan Beller [this message]
2018-08-14 23:12 ` Jonathan Nieder
2018-08-14 23:18 ` Stefan Beller
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='CAGZ79kYbmTXXwWO6Sy5ytOLS6=p=9gMzgbjdrSbJPkkQqsyJTA@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@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.
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).