All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org,  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, 03 Oct 2024 10:23:52 -0700	[thread overview]
Message-ID: <xmqqo741hzh3.fsf@gitster.g> (raw)
In-Reply-To: <88a13b9f2b6e7fbed517a7e268e4e371d84a9a10.1727917792.git.me@ttaylorr.com> (Taylor Blau's message of "Wed, 2 Oct 2024 21:09:56 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> (This bit me during the first integration round I did as interim
> maintainer[1] involved a lot of manual clean-up. More recently it has
> come up as part of a research effort to better understand a patch's
> lifecycle on the list[2].)

Thanks.


  reply	other threads:[~2024-10-03 17:23 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 [this message]
2024-10-03 18:32       ` Ramsay Jones
2024-10-03 18:44         ` Taylor Blau
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=xmqqo741hzh3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=me@ttaylorr.com \
    --cc=nasamuffin@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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.