git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <jch@google.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2022, #05; Sun, 17)
Date: Mon, 18 Jul 2022 09:11:43 -0700	[thread overview]
Message-ID: <07097797-40d7-022d-a41b-1d219183b4a5@github.com> (raw)
In-Reply-To: <xmqq7d4bt8n4.fsf@gitster.g>

Junio C Hamano wrote:
> Here are the topics that have been cooking in my tree.  Commits
> prefixed with '+' are in 'next' (being in 'next' is a sign that a
> topic is stable enough to be used and are candidate to be in a
> future release).  Commits prefixed with '-' are only in 'seen',
> and aren't considered "accepted" at all.
> 
> Copies of the source code to Git live in many repositories, and the
> following is a list of the ones I push into or their mirrors.  Some
> repositories have only a subset of branches.
> 
> With maint, master, next, seen, todo:
> 
> 	git://git.kernel.org/pub/scm/git/git.git/
> 	git://repo.or.cz/alt-git.git/
> 	https://kernel.googlesource.com/pub/scm/git/git/
> 	https://github.com/git/git/
> 	https://gitlab.com/git-vcs/git/
> 
> With all the integration branches and topics broken out:
> 
> 	https://github.com/gitster/git/
> 
> Even though the preformatted documentation in HTML and man format
> are not sources, they are published in these repositories for
> convenience (replace "htmldocs" with "manpages" for the manual
> pages):
> 
> 	git://git.kernel.org/pub/scm/git/git-htmldocs.git/
> 	https://github.com/gitster/git-htmldocs.git/
> 
> Release tarballs are available at:
> 
> 	https://www.kernel.org/pub/software/scm/git/
> 

...

> --------------------------------------------------
> [New Topics]
> 

I have a topic (formerly RFC, now a two-patch doc update) [1] that's had
some review, but isn't tracked here yet. Would you mind including it in your
next update? If not, please let me know what I should do to unblock it.

Thanks!

[1] https://lore.kernel.org/git/pull.1275.v2.git.1657584367.gitgitgadget@gmail.com/

  parent reply	other threads:[~2022-07-18 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  3:14 What's cooking in git.git (Jul 2022, #05; Sun, 17) Junio C Hamano
2022-07-18  8:29 ` zh/ls-files-format (was: What's cooking in git.git (Jul 2022, #05; Sun, 17)) Ævar Arnfjörð Bjarmason
2022-07-18 10:15 ` jk/diff-files-cleanup-fix + related un-picked-up ab/* " Ævar Arnfjörð Bjarmason
2022-07-18 17:25   ` jk/diff-files-cleanup-fix + related un-picked-up ab/* Junio C Hamano
2022-07-18 16:11 ` Victoria Dye [this message]
2022-07-18 20:24   ` What's cooking in git.git (Jul 2022, #05; Sun, 17) Junio C Hamano

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=07097797-40d7-022d-a41b-1d219183b4a5@github.com \
    --to=vdye@github.com \
    --cc=git@vger.kernel.org \
    --cc=jch@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.
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).