You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Davide Giannella <da...@apache.org> on 2015/08/05 22:17:40 UTC
ease new-comers
Hello team,
to ease new-comers I put down a page on oak docs about how to use the
combination of git and git-svn for developing/contributing to oak either
by committing to svn or producing patches.
http://jackrabbit.apache.org/oak/docs/developing-with-git.html
reviews are welcome.
Cheers
Davide
Re: ease new-comers
Posted by Michael Dürig <md...@apache.org>.
On 6.8.15 1:17 , Davide Giannella wrote:
> On 06/08/2015 10:17, Michael Dürig wrote:
>>
>> Thanks Davide for the writeup. This pretty much matches the workflow
>> I've been using for years now and which works great.
>>
>> On a side note: if you want to checkout a svn branch through git svn
>> you might first have to fetch it:
>>
>> git svn fetch --log-window-size 10000
>>
>> afterwards you can
>>
>> git checkout a-new-branch
>>
>> the new branch.
>
> Yes you can! :)
>
> I didn't write it as I personally never use it. Normally I use the
> git-svn approach for development/bug fixing on trunk. For backports I
> tend to work directly with svn on a separate checkout. As well as when
> performing releases; I do them from a straight svn checkout. Maybe I'm
> paranoid but I prefer to limit factors :)
>
I'm only using it to look at branches. Never committed anything back for
the same paranoia as you have ;-)
Michael
Re: ease new-comers
Posted by Davide Giannella <da...@apache.org>.
On 06/08/2015 10:17, Michael Dürig wrote:
>
> Thanks Davide for the writeup. This pretty much matches the workflow
> I've been using for years now and which works great.
>
> On a side note: if you want to checkout a svn branch through git svn
> you might first have to fetch it:
>
> git svn fetch --log-window-size 10000
>
> afterwards you can
>
> git checkout a-new-branch
>
> the new branch.
Yes you can! :)
I didn't write it as I personally never use it. Normally I use the
git-svn approach for development/bug fixing on trunk. For backports I
tend to work directly with svn on a separate checkout. As well as when
performing releases; I do them from a straight svn checkout. Maybe I'm
paranoid but I prefer to limit factors :)
Davide
Re: ease new-comers
Posted by Michael Dürig <md...@apache.org>.
Thanks Davide for the writeup. This pretty much matches the workflow
I've been using for years now and which works great.
On a side note: if you want to checkout a svn branch through git svn you
might first have to fetch it:
git svn fetch --log-window-size 10000
afterwards you can
git checkout a-new-branch
the new branch.
Michael
On 5.8.15 10:17 , Davide Giannella wrote:
> Hello team,
>
> to ease new-comers I put down a page on oak docs about how to use the
> combination of git and git-svn for developing/contributing to oak either
> by committing to svn or producing patches.
>
> http://jackrabbit.apache.org/oak/docs/developing-with-git.html
>
> reviews are welcome.
>
> Cheers
> Davide
>
>
Re: ease new-comers
Posted by Francesco Mari <ma...@gmail.com>.
Thanks for writing it down! I will try the steps on my machine as soon
as possible.
2015-08-05 22:17 GMT+02:00 Davide Giannella <da...@apache.org>:
> Hello team,
>
> to ease new-comers I put down a page on oak docs about how to use the
> combination of git and git-svn for developing/contributing to oak either
> by committing to svn or producing patches.
>
> http://jackrabbit.apache.org/oak/docs/developing-with-git.html
>
> reviews are welcome.
>
> Cheers
> Davide
>
>