cpp-netlib-devel

[cpp-netlib-devel] Get Git or Stay with SVN?

[Dean M. B. <mik...@gm...>]

Hi Guys,

I just wanted to throw it out there -- I'm considering using Git
instead of SVN with developing cpp-netlib. Are there any objections to
this?

Recently Sourceforge just supported Git as one of the repository
options for projects. Do you think this would work better for us, or
would we be alienating Windows developers/users?

Hope to hear from you guys soon!

-- 
Dean Michael Berris | Software Engineer, Friendster, Inc.
blog.cplusplus-soup.com | twitter.com/mikhailberis |
linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis |
deanberris.com

Re: [cpp-netlib-devel] Get Git or Stay with SVN?

[Glyn M. <gly...@gm...>]

Hi Dean,

2009/3/4 Dean Michael Berris <mik...@gm...>

> Hi Guys,
>
> I just wanted to throw it out there -- I'm considering using Git
> instead of SVN with developing cpp-netlib. Are there any objections to
> this?
>

I'm interested but I don't know a lot about Git.  Could you give a list of
advantages?


>
> Recently Sourceforge just supported Git as one of the repository
> options for projects. Do you think this would work better for us, or
> would we be alienating Windows developers/users?
>

Is there no port for Git on Windows?  If it makes development on Windows
more difficult then it would be a big disadvantage because cpp-netlib should
be cross platform.

Glyn

Re: [cpp-netlib-devel] Get Git or Stay with SVN?

[Dean M. B. <mik...@gm...>]

On Wed, Mar 4, 2009 at 6:24 PM, Glyn Matthews <gly...@gm...> wrote:
> Hi Dean,
>
> 2009/3/4 Dean Michael Berris <mik...@gm...>
>>
>> Hi Guys,
>>
>> I just wanted to throw it out there -- I'm considering using Git
>> instead of SVN with developing cpp-netlib. Are there any objections to
>> this?
>
> I'm interested but I don't know a lot about Git.  Could you give a list of
> advantages?
>

One of the advantages is local commits -- or offline commits -- which
allows for disconnected development.

Another is the distributed aspect which allows everyone to have a copy
of the *repository* not just the local copy of the source. So you can
switch between branches, merge changes easily between and across
branches, etc.

Yet another is an easy means for developing a release tar-ball with
the correct changelog from commit messages. :-)

>>
>> Recently Sourceforge just supported Git as one of the repository
>> options for projects. Do you think this would work better for us, or
>> would we be alienating Windows developers/users?
>
> Is there no port for Git on Windows?  If it makes development on Windows
> more difficult then it would be a big disadvantage because cpp-netlib should
> be cross platform.
>

I hear there are a few projects out there which allows for using Git
on Windows -- but none of them I tried.

I'm personally using git-svn now with another project, and I'm trying
out git-svn to develop cpp-netlib further -- I'm thinking of merging
John's work into the http_integration branch -- and seeing whether I
can continue his work to support persistent connections and what not.

So if we can stay with svn at Subversion, I don't mind but I
personally like developing on a Git repository from my VM. ;-)

-- 
Dean Michael Berris | Software Engineer, Friendster, Inc.
blog.cplusplus-soup.com | twitter.com/mikhailberis |
linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis |
deanberris.com

Re: [cpp-netlib-devel] Get Git or Stay with SVN?

[Glyn M. <gly...@gm...>]

Dean,

2009/3/4 Dean Michael Berris <mik...@gm...>

> On Wed, Mar 4, 2009 at 6:24 PM, Glyn Matthews <gly...@gm...>
> wrote:
> > I'm interested but I don't know a lot about Git.  Could you give a list
> of
> > advantages?
> >
>
> One of the advantages is local commits -- or offline commits -- which
> allows for disconnected development.
>
> Another is the distributed aspect which allows everyone to have a copy
> of the *repository* not just the local copy of the source. So you can
> switch between branches, merge changes easily between and across
> branches, etc.
>
> Yet another is an easy means for developing a release tar-ball with
> the correct changelog from commit messages. :-)
>

Sounds good, but I don't think its enough on its own to change the
repository.


> I'm personally using git-svn now with another project, and I'm trying
> out git-svn to develop cpp-netlib further -- I'm thinking of merging
> John's work into the http_integration branch -- and seeing whether I
> can continue his work to support persistent connections and what not.
>

Oooh it sounds like progress.  Also, don't forget there is some useful URI
code gathering dust that should be merged into trunk.


>
> So if we can stay with svn at Subversion, I don't mind but I
> personally like developing on a Git repository from my VM. ;-)
>


Even if we don't use it for this project, it might make an useful blog post
;)

G

Re: [cpp-netlib-devel] Get Git or Stay with SVN?

[Dean M. B. <mik...@gm...>]

On Wed, Mar 4, 2009 at 7:25 PM, Glyn Matthews <gly...@gm...> wrote:
> Dean,
>
> 2009/3/4 Dean Michael Berris <mik...@gm...>
>>
>> On Wed, Mar 4, 2009 at 6:24 PM, Glyn Matthews <gly...@gm...>
>> wrote:
>> > I'm interested but I don't know a lot about Git.  Could you give a list
>> > of
>> > advantages?
>> >
>>
>> One of the advantages is local commits -- or offline commits -- which
>> allows for disconnected development.
>>
>> Another is the distributed aspect which allows everyone to have a copy
>> of the *repository* not just the local copy of the source. So you can
>> switch between branches, merge changes easily between and across
>> branches, etc.
>>
>> Yet another is an easy means for developing a release tar-ball with
>> the correct changelog from commit messages. :-)
>
> Sounds good, but I don't think its enough on its own to change the
> repository.
>

Yeah, now that I think about it more, I agree. :-)

>>
>> I'm personally using git-svn now with another project, and I'm trying
>> out git-svn to develop cpp-netlib further -- I'm thinking of merging
>> John's work into the http_integration branch -- and seeing whether I
>> can continue his work to support persistent connections and what not.
>
> Oooh it sounds like progress.  Also, don't forget there is some useful URI
> code gathering dust that should be merged into trunk.
>

Oh yes. I'm also thinking of picking it up and adding more tests to it
before I merge to http_integration and then into trunk. I want the
request object constructor to take a uri object that's constructed
(implicitly) from a string or char const *. Hopefully it won't be as
hard as I think it would be. ;-)

>>
>> So if we can stay with svn at Subversion, I don't mind but I
>> personally like developing on a Git repository from my VM. ;-)
>
>
> Even if we don't use it for this project, it might make an useful blog post
> ;)
>

Yeah. :-) I might write it one day when I get more into the groove of
doing it better. ;-)

-- 
Dean Michael Berris | Software Engineer, Friendster, Inc.
blog.cplusplus-soup.com | twitter.com/mikhailberis |
linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis |
deanberris.com