All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)
Date: Mon, 03 Jul 2017 13:19:46 -0700	[thread overview]
Message-ID: <xmqqfuedl1ct.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <C31723137B784D54A3CDB1B7D9432D7E@PhilipOakley> (Philip Oakley's message of "Mon, 3 Jul 2017 20:13:02 +0100")

"Philip Oakley" <philipoakley@iee.org> writes:

> Am I right that the What's cooking  is prepared by a script?

Because I have to keep track of so many topics, its maintenance is
heavily helped by a script. I do not think it is sensible to expect
me to (or it would be good use of my time) correctly update the list
of commits manually every time a topic is replaced with its new
version.

But I consider the use of the script just like my use of Emacs to
edit the final end result.  Yes, I use tools to prepare it, and the
tools know certain rules that I prefer to apply to the document,
such as "a topic that has not been touched since the previous issue
by default does not need its description updated."

Does that answer your question?


  reply	other threads:[~2017-07-03 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 21:51 What's cooking in git.git (Jun 2017, #09; Fri, 30) Junio C Hamano
2017-07-01  7:39 ` Ævar Arnfjörð Bjarmason
2017-07-01 12:59   ` Torsten Bögershausen
2017-07-05 16:22   ` Junio C Hamano
2017-07-02 14:26 ` Philip Oakley
2017-07-03 18:20   ` Junio C Hamano
2017-07-03 19:13     ` Philip Oakley
2017-07-03 20:19       ` Junio C Hamano [this message]
2017-07-05  7:30         ` Philip Oakley
2017-07-04  6:02       ` Junio C Hamano
2017-07-05  0:17         ` Stefan Beller

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=xmqqfuedl1ct.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.org \
    /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.