Okay cool, thanks. My concern was that we were developing code away from the ASF Git repository. Which is always a temptation with DVCS systems. We absolutely must not do this. It is one of the stipulations of using Git responsibly at Apache. Code should be checked in early, and often, so that the community can comment on it in bite-sized amounts. Monolithic patches that land out of the middle of nowhere from someone's (local) private branch are Not Cool™. Seems we're cool though! :-)
On Thu, Oct 4, 2012 at 11:48 AM, Prasanna Santhanam < [email protected]> wrote: > There is no "private" branch. Just a topic branch for autoscale on the > asf repos. > > It was decided to have docs in a single branch earlier as discussed > here: http://incubator.markmail.org/thread/mmke3j2bnqosfaeg > > And merge into the impending release branch before the release. > > -- > Prasanna., > > On Thu, Oct 04, 2012 at 06:08:53AM -0400, Noah Slater wrote: > > Just following up on this. What is a "private" branch? > > > > On Tue, Sep 25, 2012 at 9:26 AM, Noah Slater <[email protected]> > wrote: > > > > > Can you clarify what you mean as "a private" branch? > > > > > > > > > On Tue, Sep 11, 2012 at 10:28 AM, Radhika Puthiyetath < > > > [email protected]> wrote: > > > > > >> Hello Community, > > >> > > >> Here is one question: AutoScale code is committed to a private branch. > > >> Where the autoscale documentation should go ? > > >> > > >> Documentation does not have a private branch yet. Therefore, I have > > >> pushed the AutoScale documentation to the master branch as of now. > Do I > > >> need to revert it ? > > >> > > >> Looking forward to the right direction in this matter. > > >> > > >> Thanks > > >> -Radhika > > >> > > >> > > >> > > -- NS
