From: Mike Ralphson <mike.ralphson@gmail.com>
Date: Thu, 15 May 2008 10:16:27 GMT
Subject: Re: [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace.
Message-ID: <e2b179460805150316n77513037y5409042b01170d4e@mail.gmail.com>
In-Reply-To: <e2b179460805131110k3cf582fdn9b8bd31046b90ca7@mail.gmail.com>

2008/5/13 Mike Ralphson <mike.ralphson@gmail.com>:
> Thanks - that was a helpful spur to action. I'll check tomorrow how it
> fairs pulling, building, running the tests etc. I've added a couple of
> 'try git tag -f's to it, so I have KNOWN_BUILDING and KNOWN_PASSING
> points to pass quickly into bisect if necessary.

My KNOWN_BUILDING and KNOWN_PASSING tags are now happily chasing each
other up the commit log.

Which branch(es) would it be most useful on which to have this
automated build/test cycle?

Although the list of tags might get slightly unwieldy (i.e. the top
commit will gain a lot of tags if all is well), with a sensible naming
convention, these tags could be pushed to a central repo (a regularly
updated clone of git.git) allowing easy visibility of the current
state of the 'build collective'.

Something like {intials}_{uname info}_{branch}_KNOWN_{BUILDING|PASSING} ?

Mike