From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Michael Rienstra <mrienstra@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: Markdown release notes
Date: Fri, 10 Feb 2023 14:20:46 +0100 [thread overview]
Message-ID: <230210.86wn4pveny.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CABBAUFKv64xhJtwRk9kMWBov=nV_QzvR-jJqhJxKQyej3pcYCQ@mail.gmail.com>
On Thu, Feb 09 2023, Michael Rienstra wrote:
> Unless I'm mistaken: Right now, release notes are only in the
> `git/git` repo, which is what git-scm.com links to. They are not
> stored in the `git/git-scm` repo.
Yes, but when we deploy git-scm.com we pull in git.git.
> Sounds like you're suggesting either (A) migrating them to the
> `git/git-scm` repo,
Definitely not this.
> (B) having them in both repos, or
Not this
> (C) displaying
> them on git-scm.com, but the underlying files would be retrieved from
> the `git/git` repo as part of the build pipeline for git-scm.com (so
> to speak). "C" sounds like the cleanest path forward, as it wouldn't
> involve any duplication or breakage.
Yeah, and most of that pipeline is set up already. I think it would be
valuable to render these release notes on that site. Thanks for working
on this.
prev parent reply other threads:[~2023-02-10 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 22:15 Markdown release notes Michael Rienstra
2023-02-09 22:31 ` brian m. carlson
2023-02-10 0:09 ` Michael Rienstra
2023-02-10 0:12 ` Michael Rienstra
2023-02-10 13:20 ` Ævar Arnfjörð Bjarmason [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
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=230210.86wn4pveny.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=mrienstra@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).