Hi all,

As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.

Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.

If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git to the git-wip-us repo.

All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
$> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git

and then set the current branch to track the corresponding branch from the flume-git repo:
$> git branch --set-upstream <branch_name> flume-git/<branch_name>.

Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/

If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.

Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!

Thanks,
Hari
--
Hari Shreedharan

Thank you very much Hari for making this happen!

Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)

Jarcec

On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> Hi all,
>
> As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
>
> Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
>
> If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git to the git-wip-us repo.
>
> All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
>
> and then set the current branch to track the corresponding branch from the flume-git repo:
> $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
>
> Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
>
> If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
>
> Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
>
> Thanks,
> Hari
> --
> Hari Shreedharan
>

Jarcec,

The site and dist directories are currently not on the git-wip-us. My belief is that they will stay on svn. I will confirm with INFRA anyway.

Thanks
Hari

--
Hari Shreedharan
On Monday, July 30, 2012 at 12:31 PM, Jarek Jarcec Cecho wrote:

> Thank you very much Hari for making this happen!
>
> Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
>
> Jarcec
>
> On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> > Hi all,
> >
> > As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
> >
> > Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
> >
> > If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git (http://git.apache.org/flume.git) to the git-wip-us repo.
> >
> > All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> > $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
> >
> > and then set the current branch to track the corresponding branch from the flume-git repo:
> > $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
> >
> > Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
> >
> > If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
> >
> > Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
> >
> > Thanks,
> > Hari
> > --
> > Hari Shreedharan
> >
>
>
>

The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git.  I suppose we should have a section on editing the web site as well.  I'm happy to add that.

Ralph
On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:

> Thank you very much Hari for making this happen!
>
> Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
>
> Jarcec
>
> On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
>> Hi all,
>>
>> As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
>>
>> Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
>>
>> If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git to the git-wip-us repo.
>>
>> All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
>> $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
>>
>> and then set the current branch to track the corresponding branch from the flume-git repo:
>> $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
>>
>> Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
>>
>> If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
>>
>> Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
>>
>> Thanks,
>> Hari
>> --
>> Hari Shreedharan
>>

Looks like I was able to commit just now!  Note that I had to setup
the .netrc file described here: https://git-wip-us.apache.org/ RHEL
6.2 with git from the repo.

Brock

On Mon, Jul 30, 2012 at 2:50 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git.  I suppose we should have a section on editing the web site as well.  I'm happy to add that.
>
> Ralph
>
>
> On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:
>
>> Thank you very much Hari for making this happen!
>>
>> Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
>>
>> Jarcec
>>
>> On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
>>> Hi all,
>>>
>>> As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
>>>
>>> Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
>>>
>>> If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git to the git-wip-us repo.
>>>
>>> All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
>>> $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
>>>
>>> and then set the current branch to track the corresponding branch from the flume-git repo:
>>> $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
>>>
>>> Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
>>>
>>> If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
>>>
>>> Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
>>>
>>> Thanks,
>>> Hari
>>> --
>>> Hari Shreedharan
>>>
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

I made some quick changes to the source.html page and published it. I believe someone already edited the wiki to reflect the move to git.
Thanks
Hari

--
Hari Shreedharan
On Monday, July 30, 2012 at 1:07 PM, Brock Noland wrote:

> Looks like I was able to commit just now! Note that I had to setup
> the .netrc file described here: https://git-wip-us.apache.org/ RHEL
> 6.2 with git from the repo.
>
> Brock
>
> On Mon, Jul 30, 2012 at 2:50 PM, Ralph Goers <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git. I suppose we should have a section on editing the web site as well. I'm happy to add that.
> >
> > Ralph
> >
> >
> > On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:
> >
> > > Thank you very much Hari for making this happen!
> > >
> > > Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
> > >
> > > Jarcec
> > >
> > > On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> > > > Hi all,
> > > >
> > > > As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
> > > >
> > > > Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
> > > >
> > > > If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git (http://git.apache.org/flume.git) to the git-wip-us repo.
> > > >
> > > > All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> > > > $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
> > > >
> > > > and then set the current branch to track the corresponding branch from the flume-git repo:
> > > > $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
> > > >
> > > > Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
> > > >
> > > > If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
> > > >
> > > > Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
> > > >
> > > > Thanks,
> > > > Hari
> > > > --
> > > > Hari Shreedharan
> > > >
> > >
> > >
> >
> >
>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
>

FYI: As of now git.apache.org/flume.git still mirrors the svn repo. This will be left as is for another 24 hours, after which it will no longer sync automatically with the svn repo, and any commits made to the svn repo may not be available on the git repo.

Thanks
Hari

--
Hari Shreedharan
On Monday, July 30, 2012 at 3:43 PM, Hari Shreedharan wrote:

> I made some quick changes to the source.html page and published it. I believe someone already edited the wiki to reflect the move to git.
>
>
> Thanks
> Hari
>
> --
> Hari Shreedharan
>
>
> On Monday, July 30, 2012 at 1:07 PM, Brock Noland wrote:
>
> > Looks like I was able to commit just now! Note that I had to setup
> > the .netrc file described here: https://git-wip-us.apache.org/ RHEL
> > 6.2 with git from the repo.
> >
> > Brock
> >
> > On Mon, Jul 30, 2012 at 2:50 PM, Ralph Goers <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git. I suppose we should have a section on editing the web site as well. I'm happy to add that.
> > >
> > > Ralph
> > >
> > >
> > > On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:
> > >
> > > > Thank you very much Hari for making this happen!
> > > >
> > > > Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
> > > >
> > > > Jarcec
> > > >
> > > > On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> > > > > Hi all,
> > > > >
> > > > > As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
> > > > >
> > > > > Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
> > > > >
> > > > > If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git (http://git.apache.org/flume.git) to the git-wip-us repo.
> > > > >
> > > > > All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> > > > > $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
> > > > >
> > > > > and then set the current branch to track the corresponding branch from the flume-git repo:
> > > > > $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
> > > > >
> > > > > Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
> > > > >
> > > > > If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
> > > > >
> > > > > Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > > --
> > > > > Hari Shreedharan
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
> > --
> > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
> >
> >
> >
>
>

SVN auto sync with git.apache.org/flume.git has been turned off, and git.apache.org/flume.git and 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 as the svn repo).
Thanks,
Hari

--
Hari Shreedharan
On Monday, July 30, 2012 at 5:01 PM, Hari Shreedharan wrote:

> FYI: As of now git.apache.org/flume.git (http://git.apache.org/flume.git) still mirrors the svn repo. This will be left as is for another 24 hours, after which it will no longer sync automatically with the svn repo, and any commits made to the svn repo may not be available on the git repo.
>
> Thanks
> Hari
>
> --
> Hari Shreedharan
>
>
> On Monday, July 30, 2012 at 3:43 PM, Hari Shreedharan wrote:
>
> > I made some quick changes to the source.html page and published it. I believe someone already edited the wiki to reflect the move to git.
> >
> >
> > Thanks
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Monday, July 30, 2012 at 1:07 PM, Brock Noland wrote:
> >
> > > Looks like I was able to commit just now! Note that I had to setup
> > > the .netrc file described here: https://git-wip-us.apache.org/ RHEL
> > > 6.2 with git from the repo.
> > >
> > > Brock
> > >
> > > On Mon, Jul 30, 2012 at 2:50 PM, Ralph Goers <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git. I suppose we should have a section on editing the web site as well. I'm happy to add that.
> > > >
> > > > Ralph
> > > >
> > > >
> > > > On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:
> > > >
> > > > > Thank you very much Hari for making this happen!
> > > > >
> > > > > Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
> > > > >
> > > > > Jarcec
> > > > >
> > > > > On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
> > > > > >
> > > > > > Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
> > > > > >
> > > > > > If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git (http://git.apache.org/flume.git) to the git-wip-us repo.
> > > > > >
> > > > > > All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> > > > > > $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
> > > > > >
> > > > > > and then set the current branch to track the corresponding branch from the flume-git repo:
> > > > > > $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
> > > > > >
> > > > > > Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
> > > > > >
> > > > > > If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.

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 has been turned off, and git.apache.org/flume.git and 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 as the svn repo).
>
>
> Thanks,
> Hari
>
>
>

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
>

Thanks Ralph. I can work on the source.html page and modify it to reflect git.  

Thanks,
Hari

--
Hari Shreedharan
On Monday, July 30, 2012 at 12:50 PM, Ralph Goers wrote:

> The CMS is built on top of svn so I'm pretty sure the site has to stay on git. However, http://flume.apache.org/source.html should be modified to reflect using git. I suppose we should have a section on editing the web site as well. I'm happy to add that.
>
> Ralph
>
>
> On Jul 30, 2012, at 12:31 PM, Jarek Jarcec Cecho wrote:
>
> > Thank you very much Hari for making this happen!
> >
> > Are we also going to move site generation to git or will it remain in svn? The reason why I'm asking is that we should update repository path on web pages :-)
> >
> > Jarcec
> >
> > On Mon, Jul 30, 2012 at 12:18:20PM -0700, Hari Shreedharan wrote:
> > > Hi all,
> > >
> > > As promised a few weeks back, Apache Flume's primary code repository is now on Apache git-wip-us: https://git-wip-us.apache.org/repos/asf/flume.git.
> > >
> > > Please make sure all commits are made to this repo from now on. I have cherry-picked the latest commit on SVN to the git repo, and Jukka had clone the repo till the last commit made yesterday. All committers, please make sure you commit to this repo and NOT to SVN. Any commits made to SVN will not be reflected here automatically.
> > >
> > > If you do commit to SVN, please make sure you cherry pick the commit from git.apache.org/flume.git (http://git.apache.org/flume.git) to the git-wip-us repo.
> > >
> > > All developers: you can switch your current branch to point to the new git repo by first adding this repo as a new remote, say "flume-wip":
> > > $> git remote add flume-git https://git-wip-us.apache.org/repos/asf/flume.git
> > >
> > > and then set the current branch to track the corresponding branch from the flume-git repo:
> > > $> git branch --set-upstream <branch_name> flume-git/<branch_name>.
> > >
> > > Please note that git has an asymmetry between git pull and git push: http://longair.net/blog/2011/02/27/an-asymmetry-between-git-pull-and-git-push/
> > >
> > > If you are confused by all this, simply clone the new repo into a new directory. It has all the branches and all commits made to trunk. You can simply create a patch from your current work and apply it to the new directory. This is also the simplest thing to do.
> > >
> > > Thanks to the Apache INFRA team, in particular Jukka Zitting and Joe Schaefer for making this possible!
> > >
> > > Thanks,
> > > Hari
> > > --
> > > Hari Shreedharan
> > >
> >
> >
>
>
>