From: Junio C Hamano <gitster@pobox.com>
To: "R. Tyler Ballance" <tyler@slide.com>
Cc: git@vger.kernel.org
Subject: Re: Using the "What's cooking" scripts outside of Git
Date: Mon, 26 Jan 2009 12:15:31 -0800 [thread overview]
Message-ID: <7vzlhd4ye4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1232997904.22352.4041.camel@starfruit> (R. Tyler Ballance's message of "Mon, 26 Jan 2009 11:25:04 -0800")
"R. Tyler Ballance" <tyler@slide.com> writes:
> I was toying around with the idea of generating a "What's cooking" email
> similar to Junio's for our internal development, and I'm wondering if
> anybody has any experience using the scripts outside of the standard Git
> repository.
>
> Our repo is laid out slightly different, there's no "next" branch but
> there are a number of "in development" branches that get folded down
> into master.
UTSL, it's all open source ;-)
It is generated by the toolchain I check out in Meta/ directory from the
'todo' branch of git.git. Of interest would be
- git-topic.perl -- this lists the topics with their doneness. It
unfortunately heavily depends on my workflow to have one stable
('next') and one wilder ('pu') test integration branches, and
convention to name the topics as ??/?*.
- WC -- this produces and helps me maintain "What's cooking". It calls
git-topic.perl to generate the list, and optionally calls UWC to merge
the new one with the previous issue.
- UWC -- this reads the last issue of "What's cooking", and uses the
output from git-topic.perl to update it. It primarily is needed
because the order topics are output from git-topic.perl is different
from how I want to have them listed in "What's cooking", and reads the
last issue to classify each topics into the same category as they
appeared in it.
- WI -- this gives "What's in" and should be straightforward.
prev parent reply other threads:[~2009-01-26 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:25 Using the "What's cooking" scripts outside of Git R. Tyler Ballance
2009-01-26 20:15 ` Junio C Hamano [this message]
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=7vzlhd4ye4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tyler@slide.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).