[dev] [commits] Horde-Support branch master updated. 744c5e27ae3f7f271c2d897ec0a31688f6e61d5f

[Michael Rubinsky]

Quoting Michael Rubinsky <mike at theupstairsroom.com>:

> The branch "master" has been updated.
> The following is a summary of the commits.
>
> from: 881c63f4b897e5084c22dc5e8c898151c8e55376
>
> 744c5e2 Make sure this script is run in bash, not any shell that  
> /bin/sh points to.
>
> -----------------------------------------------------------------------
>
> commit 744c5e27ae3f7f271c2d897ec0a31688f6e61d5f
> Author: Michael Rubinsky <mrubinsk at simon.horde.org>
> Date:   Thu Jan 14 16:10:19 2010 +0000
>
>     Make sure this script is run in bash, not any shell that /bin/sh  
> points to.
>
>     Countless hours to figure out the problem was simply that  
> /bin/sh points to a
>     dash shell on ubuntu now...and their are enough differnces to  
> cause big problems.
>
>     Tweak some statements to make them clearer and avoid some errors  
> from expr.

Ok. This should be all set and working properly now. Any commits that  
result in the same delta being applied to [topic branch] that has  
already been applied to master will be ignored in the commit email, so  
we can now happily go along and keep our remote topic branches up to  
date with master (as now explained at http://horde.org/source/git.php)  
without getting distracting, irrelevant commit messages.

Would still like to produce a line in the email that says something to  
the effect that "x number of commits were silenced since they are the  
result of a rebase from master" or similar....but that is for a  
different day.

I've tested this locally, remotely on a temporary repo on simon, and  
on the live repo. That being said, would probably be a good idea to  
keep an extra keen eye on the commit messages generated by our pushes  
for the next day or so, just in case :)

Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin