From: "R. Tyler Ballance" <tyler@slide.com>
To: git@vger.kernel.org
Subject: Using the "What's cooking" scripts outside of Git
Date: Mon, 26 Jan 2009 11:25:04 -0800 [thread overview]
Message-ID: <1232997904.22352.4041.camel@starfruit> (raw)
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
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.
Any tips would be appreciated
Cheers
--
-R. Tyler Ballance
Slide, Inc.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-01-26 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:25 R. Tyler Ballance [this message]
2009-01-26 20:15 ` Using the "What's cooking" scripts outside of Git Junio C Hamano
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=1232997904.22352.4041.camel@starfruit \
--to=tyler@slide.com \
--cc=git@vger.kernel.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 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).