This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-git".

The branch, master has been updated
       via  dd039671442a3a340b788037c0ce9dd546edad17 (commit)
       via  bc7088732d3a0289b1a2dcce2ade9d23604b68d8 (commit)
       via  dd2a054239473a4a32773d3579f024c771f80245 (commit)
      from  880ef03a03f90e48397be153cf1753c7e2c89ed5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit dd039671442a3a340b788037c0ce9dd546edad17
Merge: bc7088732d3a0289b1a2dcce2ade9d23604b68d8 
880ef03a03f90e48397be153cf1753c7e2c89ed5
Author: Paul Hammant <p...@hammant.org>
Date:   Sat Apr 3 20:27:56 2010 -0500

    Merge branch 'master' of ssh://git.codehaus.org/jbehave-git

commit bc7088732d3a0289b1a2dcce2ade9d23604b68d8
Author: Paul Hammant <p...@hammant.org>
Date:   Sat Apr 3 20:27:35 2010 -0500

    tables can be formatted better for reading

commit dd2a054239473a4a32773d3579f024c771f80245
Author: Paul Hammant <p...@hammant.org>
Date:   Sat Apr 3 17:36:51 2010 -0500

    rename for clarity

-----------------------------------------------------------------------

Summary of changes:
 .../org/jbehave/examples/trader/TraderSteps.java   |    4 ++--
 .../trader/stories/claims_with_null_calendar.story |    6 +++---
 .../trader/stories/given_non_successful.story      |   10 +++++-----
 .../examples/trader/stories/non_successful.story   |   16 ++++++++--------
 .../stories/trader_is_alerted_of_status.story      |    6 +++---
 .../examples/trader/stories/wildcard_search.story  |    6 +++---
 6 files changed, 24 insertions(+), 24 deletions(-)


hooks/post-receive
-- 
jbehave-git

<hr/>
<p>
To unsubscribe from this list please visit:
</p>
<p>
    <a 
href="http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email</a>

Reply via email to