From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [announce] gc
Date: Wed, 14 Jan 2009 02:31:18 +0100 [thread overview]
Message-ID: <gkjf93$r5e$1@ger.gmane.org> (raw)
In-Reply-To: 20081222212407.47c9ab1e.stephen@exigencecorp.com
Stephen Haberman wrote:
> This is just a small collections of hooks, scripts, and practices I
> developed while working on a not-distributed/corporate project.
>
> A quick list is: svn-like revision numbers (via tagging every commit)
> (don't flame me, please), combined diff-enabled commit emails*, Hudson
> hooks, trac hooks, branch locking, same-repo-separate-DAG git
> server-side config storage and export-on-push, and developer-side
> push/pull scripts that "just work".
>
> http://github.com/stephenh/gc
>
> Hopefully others find it as useful.
Added to http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-01-14 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 3:24 [announce] gc Stephen Haberman
2008-12-23 13:13 ` Matthieu Moy
2008-12-23 14:22 ` Stephen Haberman
2008-12-23 15:06 ` Mike Ralphson
2008-12-25 15:23 ` Stephen Haberman
2009-01-14 1:31 ` Jakub Narebski [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='gkjf93$r5e$1@ger.gmane.org' \
--to=jnareb@gmail.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).