On Fri, Nov 11, 2011 at 6:18 PM, Justin Deoliveira wrote:
>
>
> On Fri, Nov 11, 2011 at 9:15 AM, Andrea Aime > wrote:
>
>> On Fri, Nov 11, 2011 at 4:33 PM, Justin Deoliveira
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira >> > wrote:
>>>
Well... for now the idea
Hi Michael,
Actually when trying to get a cloned repo linked back to svn I had a tough
time figuring out what would work. The git documentation seems to say you
can simply do the svn init and then the following:
git update-ref refs/remotes/git-svn origin/master
BUt this did not work for me. I
On Fri, Nov 11, 2011 at 9:15 AM, Andrea Aime
wrote:
> On Fri, Nov 11, 2011 at 4:33 PM, Justin Deoliveira
> wrote:
>
>>
>>
>> On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira
>> wrote:
>>
>>> Well... for now the idea is that no, you wouldn't push changes directly
>>> to this repository. What i
Hi Justin,
Sorry for this newbie question, but I'm confused about the difference
between what you first get by cloning the git repository and what you
later get by doing git svn fetch.
I understand that initial clone gives you the repo with history back
to r36490 but no link to the svn repo, henc
On Fri, Nov 11, 2011 at 4:33 PM, Justin Deoliveira wrote:
>
>
> On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira
> wrote:
>
>> Well... for now the idea is that no, you wouldn't push changes directly
>> to this repository. What i had in mind was that one would fork the repo
>> locally in his/her
On 11 November 2011 15:33, Justin Deoliveira wrote:
>
>
> On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira
> wrote:
>>
>> Well... for now the idea is that no, you wouldn't push changes directly to
>> this repository. What i had in mind was that one would fork the repo locally
>> in his/her own
On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira wrote:
> Well... for now the idea is that no, you wouldn't push changes directly to
> this repository. What i had in mind was that one would fork the repo
> locally in his/her own account, and mostly work from that. Pushing changes
> back into svn
Well... for now the idea is that no, you wouldn't push changes directly to
this repository. What i had in mind was that one would fork the repo
locally in his/her own account, and mostly work from that. Pushing changes
back into svn will still be down with an svn dcommit from your own copy,
not by
Aha, I knew it, it starts get confusing to me.
Does this mean that I can use git for geotools and push my changes to
this new repo ?.
In which direction is the synchronization between the two repos working.
svn ---> git
svn <--- git
svn <---> git (how are conflicts resolved ?)
Cheers
Christia
Hi all,
I took the liberty of trying to set up a "canonical" github repository.
https://github.com/geotools/geotools
The idea is that this would be the repository that developers fork locally
to do development like we do today. Having a same base repository makes
pushing/pulling changes back a
10 matches
Mail list logo
