Hi all,
I would like to get some suggestions and help on the matter of migrating
the code repository from SVN to GIT - the fact that such migration will
bring value is for sure :)
What things need to be sorted out when moving to GIT:
1) for backward compatibility, I would suggest having a R
2013/2/18 Bogdan-Andrei Iancu :
> Hi all,
>
> I would like to get some suggestions and help on the matter of migrating the
> code repository from SVN to GIT - the fact that such migration will bring
> value is for sure :)
YES! YES! YES!
--
With best regards, Peter Lemenkov.
___
Hi Bogdan,
On Feb 18, 2013, at 5:05 PM, Bogdan-Andrei Iancu wrote:
> Hi all,
>
> I would like to get some suggestions and help on the matter of migrating the
> code repository from SVN to GIT - the fact that such migration will bring
> value is for sure :)
>
I'm glad to see this happening. C
2013/2/18 Saúl Ibarra Corretgé :
>> What things need to be sorted out when moving to GIT:
>>
>
> First question: would it be a self-hosted Git repository or the GitHub
> service?
"Why can't we have both?"
I personally don't see any issues here - It's possible to setup a
"primary" repo at SF and
Hi Saul,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/18/2013 06:20 PM, Saúl Ibarra Corretgé wrote:
What things need to be sorted out when moving to GIT:
First question: would it be a self-hosted Git repository or the GitHub service?
1) for ba
Hi Peter,
On 02/18/2013 06:52 PM, Peter Lemenkov wrote:
2013/2/18 Saúl Ibarra Corretgé:
What things need to be sorted out when moving to GIT:
First question: would it be a self-hosted Git repository or the GitHub service?
"Why can't we have both?"
I personally don't see any issues here - I
>
> When comes to SF versus GITHUB - the main problem from my perspective is that
> SF overs a unified (one account) for tracker, forums, downloads, code
> repo.If we move code repo to GITHUB, we will force the developer to use 2
> accounts (on SF for tracker, forum , etc, and one on GITHUB
On 02/19/2013 02:36 PM, Saúl Ibarra Corretgé wrote:
When comes to SF versus GITHUB - the main problem from my perspective is that
SF overs a unified (one account) for tracker, forums, downloads, code
repo.If we move code repo to GITHUB, we will force the developer to use 2
accounts (on SF
>
> Currently, what we use from SF :
> - code repository
It's there.
> - file download system
Sort of. You can't upload files, but it will generate tar files for each tag.
> - trackers (bugs, patches, features)
It's there.
> - news system
Nope.
> - d
On Tue, 19 Feb 2013 15:45:01 +0100
Saúl Ibarra Corretgé wrote:
> > - file download system
>
> Sort of. You can't upload files, but it will generate tar files for
> each tag.
So it is not very suitable for real releases. There is no way to include
generated files that should not go to the
On Feb 20, 2013, at 9:41 AM, Jacek Konieczny wrote:
> On Tue, 19 Feb 2013 15:45:01 +0100
> Saúl Ibarra Corretgé wrote:
>>>- file download system
>>
>> Sort of. You can't upload files, but it will generate tar files for
>> each tag.
>
> So it is not very suitable for real releases. Ther
Hi,
Trying to summaries the status.
It is doable to move NEWS, Donations, file downloads and forums on
opensips.org -> this will make GITHUB is an alternative to SF, hosting
code repo and tracker.
So, after all everything reduces to GH versus SF, or what we have to
gain from GH and what to
Hi,
On Feb 28, 2013, at 2:14 PM, Bogdan-Andrei Iancu wrote:
> Hi,
>
> Trying to summaries the status.
>
> It is doable to move NEWS, Donations, file downloads and forums on
> opensips.org -> this will make GITHUB is an alternative to SF, hosting code
> repo and tracker.
>
> So, after all eve
Bogdan,
Git has pull requests as a feature, but its hard to manage without
some ecosystem like GH as saul mentioned. Here is a good response that
details the differences between what we consider a GH pull request and
a standard git pull request.
http://stackoverflow.com/questions/6235379/how-to-
> "BI" == Bogdan-Andrei Iancu writes:
BI> So, after all everything reduces to GH versus SF
It does not need to be an either-or. You can keep using SF for the
mailing lists (you should do that no matter what) and anything else
you like better.
You can keep copies of the git repo on both. M
Unless you can get over the idea of a centralized repository, GIT is
an over curve, some would say counter intuitive. Please look into
subtrees, branches, tags.
Did not have time to look at everyone's post, but I am pretty sure
everyone will be enthused about the idea. I would say, if it's not
bro
16 matches
Mail list logo
