2013/7/23 Ryan Ollos <[email protected]> > On Mon, Jul 22, 2013 at 6:38 PM, Hua Xiang <[email protected]> wrote: > > > 2013/7/23 Ryan Ollos <[email protected]> > > > > > On Mon, Jul 22, 2013 at 6:06 PM, Hua Xiang <[email protected]> > > wrote: > > > > > > > Hi! > > > > > > > > I am doing the project 'generate time series reports'. > > > > Details are: > > > > (https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008) > > > > > > > > I have created SQL statements to generate reports locally and I also > > > > committed the changes needed for display. However, I would like to > know > > > how > > > > to commit my SQL statements to the repository so that other developer > > can > > > > see my change? > > > > > > > > Thanks! > > > > > > > > Best, > > > > Hua > > > > > > > > > > > > > I had pasted a link to "ViewVC" earlier, so that could have been > > > misleading, sorry about that. > > > > > > Please try the following: > > > - $ svn co > > > > > > svn.apache.org/repos/asf/bloodhound/branches/bep_0008_time_series_reports > > > - apply your changes in the working copy > "bep_0008_time_series_reports" > > > - check-in your changes as you did earlier (but you'll be pushing to > > your > > > branch this time, not the trunk). > > > > > > > Commit failed. Please check my last email. > > > What error message do you see when the commit fails?
"Error Access to '/repos/asf/!svn/me‘ forbidden" However, I just committed to trunk successfully. > > What is the output of "svn info" on your working copy? > TortoiseSVN 1.7.13, Build 24257 - 64 Bit , 2013/06/01 07:32:54 Subversion 1.7.10, apr 1.4.6 apr-utils 1.3.12 neon 0.29.6 OpenSSL 1.0.1e 11 Feb 2013 zlib 1.2.7 > > > > Be careful about unnecessary whitespace changes. In the changeset you > > > pushed to the trunk there seemed to be a lot of unnecessary whitespace > > > changes, and the "changeset noise" makes it harder for other developers > > to > > > code review the changeset. > > > > > > Apologize. I will be careful. > > > > > > > Also, you had made some changes to the Trac > > > codebase. In most cases, it should not be necessary for you to touch > the > > > Trac code (anything under bloodhound/trac in the source code tree). > There > > > are some exceptions to this, and we can help you work through this > after > > > you publish your changes. > > > > > > > I did changes on api.py and report.py in order to map report column names > > and provide correct time format. > > I will explain this later. > > > > > > -- > Ryan Ollos I *Apache Bloodhound Committer* > > WANdisco // *Non-Stop Data* > > e. [email protected] > twitter @rjollos <https://twitter.com/rjollos> > > THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE > PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its > subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. > If you are not the intended recipient, please notify us immediately and > destroy the message without disclosing its contents to anyone. Any > distribution, use or copying of this e-mail or the information it contains > by other than an intended recipient is unauthorized. The views and > opinions expressed in this e-mail message are the author's own and may not > reflect the views and opinions of WANdisco, unless the author is authorized > byWANdisco to express such views or opinions on its behalf. All email sent > to or from this address is subject to electronic storage and review by > WANdisco. Although WANdisco operates anti-virus programs, it does not > accept responsibility for any damage whatsoever caused by viruses being > passed. >
