Sorry for the noice. :) please ignore. All is well :)

I think, I did a mistake while checking out branch-2.5.
 used "git checkout *-b *branch-2.5" instead of "git checkout branch-2.5"

Regards,
Vinay


On Wed, Aug 27, 2014 at 2:52 PM, Karthik Kambatla <ka...@cloudera.com>
wrote:

> On Wed, Aug 27, 2014 at 2:19 AM, Vinayakumar B <vinayakum...@apache.org>
> wrote:
>
> > Hi Karthik,
> >
> > Good to see migration completed.
> >
> > Currently, *branch-2.5* points to *trunk *itself. I think it should point
> > to  *origin/branch-2.5 *right?
> >
>
> Are you referring to your local branch-2.5? What is origin?
>
> branch-2.5 looks good to me.
>
>
> >
> > Regards,
> > Vinay
> >
> >
> > On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla <ka...@cloudera.com>
> > wrote:
> >
> > > Oh.. a couple more things.
> > >
> > > The git commit hashes have changed and are different from what we had
> on
> > > our github. This might interfere with any build automations that folks
> > > have.
> > >
> > > Another follow-up item: email and JIRA integration
> > >
> > >
> > > On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla <ka...@cloudera.com>
> > > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I am very excited to let you know that the git repo is now writable.
> I
> > > > committed a few changes (CHANGES.txt fixes and branching for 2.5.1)
> and
> > > > everything looks good.
> > > >
> > > > Current status:
> > > >
> > > >    1. All branches have the same names, including trunk.
> > > >    2. Force push is disabled on trunk, branch-2 and tags.
> > > >    3. Even if you are experienced with git, take a look at
> > > >    https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
> > let
> > > >    us avoid merge commits.
> > > >
> > > > Follow-up items:
> > > >
> > > >    1. Update rest of the wiki documentation
> > > >    2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > > >    (reviews appreciated). Until this is done, the precommit jobs will
> > run
> > > >    against our old svn repo.
> > > >    3. git mirrors etc. to use the new repo instead of the old svn
> repo.
> > > >
> > > > Thanks again for your cooperation through the migration process.
> Please
> > > > reach out to me (or the list) if you find anything missing or have
> > > > suggestions.
> > > >
> > > > Cheers!
> > > > Karthik
> > > >
> > > >
> > >
> >
>

Reply via email to