All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/2] Documentation/howto/maintain-git.txt: a pair of bugfixes
Date: Tue, 1 Nov 2022 19:46:19 -0400	[thread overview]
Message-ID: <Y2GvyyG3K1OpIqAw@nand.local> (raw)
In-Reply-To: <xmqqo7tqco0y.fsf@gitster.g>

On Tue, Nov 01, 2022 at 03:23:25PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > Why not have a single file with all of the topics, with two "###"
> > markers?
>
> Mostly because jch and seen are built in two distinct steps, and I
> need to be able to rearrange lines in the redo-jch.sh file either in
> the editor or by running "Meta/redo-jch.sh -u", without touching
> what is in redo-seen.sh file (meaning: what comes after your final
> "###" cut lines).

Very helpful. Thank you :-).

Thanks,
Taylor

  reply	other threads:[~2022-11-01 23:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 23:47 [PATCH 0/2] Documentation/howto/maintain-git.txt: a pair of bugfixes Taylor Blau
2022-10-31 23:47 ` [PATCH 1/2] Documentation: build redo-jch.sh from master..jch Taylor Blau
2022-10-31 23:47 ` [PATCH 2/2] Documentation: build redo-seen.sh from jch..seen Taylor Blau
2022-11-01  8:01 ` [PATCH 0/2] Documentation/howto/maintain-git.txt: a pair of bugfixes Jeff King
2022-11-01 21:24   ` Taylor Blau
2022-11-01 22:23   ` Junio C Hamano
2022-11-01 23:46     ` Taylor Blau [this message]
2022-11-02  8:01     ` 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=Y2GvyyG3K1OpIqAw@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.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.
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.