Juhani, It seems like trunk cannot be force pushed to. So I am pinging Jukka et al, to see if we can force push just this once.
Thanks Hari -- Hari Shreedharan On Wednesday, August 15, 2012 at 12:15 AM, Juhani Connolly wrote: > I just pushed the patch for flume-1382 after switching my upstream and > using git-diff to check the contents of the changes were ok. > > The source itself seems fine, however it seems to have messed up the > change log a bit in the process with intermediate entries from local > merges(basically where I had applied a patch locally before it was > committed to the trunk... so the end reasult is the same). My sincere > apologies for this, but I would prefer to avoid worsening this, and > would appreciate if someone could undo the unnecessary commits added to > the log. I'll be changing the way I handle my local branches to avoid > such issues in the future. > > On 08/02/2012 03:44 AM, Hari Shreedharan wrote: > > SVN auto sync with git.apache.org/flume.git > > (http://git.apache.org/flume.git) has been turned off, and > > git.apache.org/flume.git (http://git.apache.org/flume.git) and > > github.com/apache/flume (http://github.com/apache/flume) will now mirror > > the new git-wip-us repo. If you still prefer to use svn, svn can be used > > with github - but it is read-only. svn.a.o/repos/asf/flume will *no longer* > > be updated. > > > > To use svn with github, please read: > > https://github.com/blog/626-announcing-svn-support > > https://github.com/blog/966-improved-subversion-client-support > > (Please use github.com/apache/flume (http://github.com/apache/flume) as the > > svn repo). > > > > > > Thanks, > > Hari >
