Preferably, yes. But for now it will suffice considering the committing frequency, imho.
On Thu, Feb 9, 2012 at 1:53 AM, Henry Saputra <[email protected]>wrote: > I think commits log should go to commits@ list, dont they? > > - Henry > > On Wed, Feb 8, 2012 at 8:50 AM, <[email protected]> wrote: > > Author: lewismc > > Date: Wed Feb 8 16:50:21 2012 > > New Revision: 1241968 > > > > URL: http://svn.apache.org/viewvc?rev=1241968&view=rev > > Log: > > trivial commit to test commit mails. > > > > Modified: > > gora/trunk/CHANGES.txt > > > > Modified: gora/trunk/CHANGES.txt > > URL: > http://svn.apache.org/viewvc/gora/trunk/CHANGES.txt?rev=1241968&r1=1241967&r2=1241968&view=diff > > > ============================================================================== > > --- gora/trunk/CHANGES.txt (original) > > +++ gora/trunk/CHANGES.txt Wed Feb 8 16:50:21 2012 > > @@ -2,6 +2,8 @@ Gora Change Log > > > > Trunk (unreleased changes): > > > > +* GORA-91 Ensure that Gora adheres to ASF branding requirements > (lewismc) > > + > > * GORA-90 Create DOAP for Gora (lewismc) > > > > * GORA-79 Block keyspace creation until the whole cassandra cluster > converges to the new keyspace. (Patricio Echagüe vis lewismc) > > > > >
