From: Taylor Blau <me@ttaylorr.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <nasamuffin@google.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v3] Documentation: mention the amlog in howto/maintain-git.txt
Date: Thu, 3 Oct 2024 14:44:12 -0400 [thread overview]
Message-ID: <Zv7l/Fw5gdkWlDxw@nand.local> (raw)
In-Reply-To: <14497a9c-8683-440e-b179-2b10b4516d9c@ramsayjones.plus.com>
On Thu, Oct 03, 2024 at 07:32:04PM +0100, Ramsay Jones wrote:
> > + [remote "github2"]
> > + url = https://github.com/git/git
> > + fetch = +refs/heads/*:refs/remotes/github2/*
> > + pushurl = github.com:git/git.git
> > + push = refs/heads/maint:refs/heads/maint
> > + push = refs/heads/master:refs/heads/master
> > + push = refs/notes/next:refs/notes/next
>
> Hmm, s/notes/heads/g perhaps?
Ugh, serves me right for trying to send this out late my time last
night.
Perhaps Junio can tweak this when applying? Otherwise I can send out a
new version.
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-03 18:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 16:21 Linking topic merges to mailing list threads Emily Shaffer
2024-09-30 16:57 ` Konstantin Ryabitsev
2024-09-30 19:30 ` Junio C Hamano
2024-09-30 20:45 ` [PATCH] Documentation: mention the amlog in howto/maintain-git.txt Taylor Blau
2024-09-30 21:06 ` Kristoffer Haugsbakk
2024-10-02 15:04 ` Taylor Blau
2024-09-30 21:54 ` Junio C Hamano
2024-10-02 15:05 ` Taylor Blau
2024-10-02 15:03 ` [PATCH v2] " Taylor Blau
2024-10-02 19:47 ` Junio C Hamano
2024-10-03 1:09 ` Taylor Blau
2024-10-03 1:09 ` [PATCH v3] " Taylor Blau
2024-10-03 17:23 ` Junio C Hamano
2024-10-03 18:32 ` Ramsay Jones
2024-10-03 18:44 ` Taylor Blau [this message]
2024-09-30 20:41 ` Linking topic merges to mailing list threads Kristoffer Haugsbakk
2024-10-02 22:50 ` Eric Wong
2024-10-02 23:34 ` Jeff King
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=Zv7l/Fw5gdkWlDxw@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=konstantin@linuxfoundation.org \
--cc=nasamuffin@google.com \
--cc=ramsay@ramsayjones.plus.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).