[Cs-dev] DVCS again

[Cs-dev] DVCS again

Date	2011-02-09 18:12
From	John ff
Subject	[Cs-dev] DVCS again
	Following all the e-mails I have been convinced that we need to move to a DVCS while continuing to use SF as the central release point. This seems to mean one of GIT Mercurial Bazaar Can we have a straw poll? I am particularly interested in the views of the regular developers, but also the wider community with interests in the code. Perhaps an order of preference if you want, or FPTP; but remember this is just a straw poll. Probably best to mail me direct, or via this list if you prefer. I will tally and report. Got to do something while we wait for CVS to return! I think I have decided my preference...... ==John ffitch ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2011-02-09 18:27
From	Victor Lazzarini
Subject	Re: [Cs-dev] DVCS again
	I would vote for GIT. Victor On 9 Feb 2011, at 18:12, John ff wrote: > Following all the e-mails I have been convinced that we need to move > to a DVCS while continuing to use SF as the central release point. > This seems to mean one of > > GIT > Mercurial > Bazaar > > Can we have a straw poll? I am particularly interested in the views > of the regular developers, but also the wider community with interests > in the code. Perhaps an order of preference if you want, or FPTP; > but remember this is just a straw poll. > > Probably best to mail me direct, or via this list if you prefer. I > will tally and report. Got to do something while we wait for CVS to > return! > > I think I have decided my preference...... > > ==John ffitch > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel > Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2011-02-09 18:34
From	Felipe Sateler
Subject	Re: [Cs-dev] DVCS again
	Git would be my choice too. On Wed, Feb 9, 2011 at 15:27, Victor Lazzarini wrote: > I would vote for GIT. > Victor > On 9 Feb 2011, at 18:12, John ff wrote: > >> Following all the e-mails I have been convinced that we need to move >> to a DVCS while continuing to use SF as the central release point. >> This seems to mean one of >> >> GIT >> Mercurial >> Bazaar >> >> Can we have a straw poll? I am particularly interested in the views >> of the regular developers, but also the wider community with interests >> in the code. Perhaps an order of preference if you want, or FPTP; >> but remember this is just a straw poll. >> >> Probably best to mail me direct, or via this list if you prefer. I >> will tally and report. Got to do something while we wait for CVS to >> return! >> >> I think I have decided my preference...... >> >> ==John ffitch >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel >> Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Saludos, Felipe Sateler ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/l

Date	2011-02-09 18:37
From	Steven Yi
Subject	Re: [Cs-dev] DVCS again
	Mercurial for me, with git as a 2nd choice. On 2/9/11, Felipe Sateler wrote: > Git would be my choice too. > > On Wed, Feb 9, 2011 at 15:27, Victor Lazzarini > wrote: >> I would vote for GIT. >> Victor >> On 9 Feb 2011, at 18:12, John ff wrote: >> >>> Following all the e-mails I have been convinced that we need to move >>> to a DVCS while continuing to use SF as the central release point. >>> This seems to mean one of >>> >>> GIT >>> Mercurial >>> Bazaar >>> >>> Can we have a straw poll? I am particularly interested in the views >>> of the regular developers, but also the wider community with interests >>> in the code. Perhaps an order of preference if you want, or FPTP; >>> but remember this is just a straw poll. >>> >>> Probably best to mail me direct, or via this list if you prefer. I >>> will tally and report. Got to do something while we wait for CVS to >>> return! >>> >>> I think I have decided my preference...... >>> >>> ==John ffitch >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel >>> Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > > > -- > > Saludos, > Felipe Sateler > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Sent from my mobile device ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2011-02-09 18:51
From	Rory Walsh
Subject	Re: [Cs-dev] DVCS again
	GIT for me. Only because I have used it before. On 9 February 2011 18:37, Steven Yi wrote: > Mercurial for me, with git as a 2nd choice. > > On 2/9/11, Felipe Sateler wrote: >> Git would be my choice too. >> >> On Wed, Feb 9, 2011 at 15:27, Victor Lazzarini >> wrote: >>> I would vote for GIT. >>> Victor >>> On 9 Feb 2011, at 18:12, John ff wrote: >>> >>>> Following all the e-mails I have been convinced that we need to move >>>> to a DVCS while continuing to use SF as the central release point. >>>> This seems to mean one of >>>> >>>> GIT >>>> Mercurial >>>> Bazaar >>>> >>>> Can we have a straw poll? I am particularly interested in the views >>>> of the regular developers, but also the wider community with interests >>>> in the code. Perhaps an order of preference if you want, or FPTP; >>>> but remember this is just a straw poll. >>>> >>>> Probably best to mail me direct, or via this list if you prefer. I >>>> will tally and report. Got to do something while we wait for CVS to >>>> return! >>>> >>>> I think I have decided my preference...... >>>> >>>> ==John ffitch >>>> >>>> ------------------------------------------------------------------------------ >>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel >>>> Studio XE: >>>> Pinpoint memory and threading errors before they happen. >>>> Find and fix more than 250 security defects in the development cycle. >>>> Locate bottlenecks in serial and parallel code that limit performance. >>>> http://p.sf.net/sfu/intel-dev2devfeb >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> >> >> -- >> >> Saludos, >> Felipe Sateler >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > -- > Sent from my mobile device > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2011-02-09 19:21
From	Michael Gogins
Subject	Re: [Cs-dev] DVCS again
	I vote for GIT. Regards, Mike On Wed, Feb 9, 2011 at 1:51 PM, Rory Walsh wrote: > GIT for me. Only because I have used it before. > > On 9 February 2011 18:37, Steven Yi wrote: >> Mercurial for me, with git as a 2nd choice. >> >> On 2/9/11, Felipe Sateler wrote: >>> Git would be my choice too. >>> >>> On Wed, Feb 9, 2011 at 15:27, Victor Lazzarini >>> wrote: >>>> I would vote for GIT. >>>> Victor >>>> On 9 Feb 2011, at 18:12, John ff wrote: >>>> >>>>> Following all the e-mails I have been convinced that we need to move >>>>> to a DVCS while continuing to use SF as the central release point. >>>>> This seems to mean one of >>>>> >>>>> GIT >>>>> Mercurial >>>>> Bazaar >>>>> >>>>> Can we have a straw poll? I am particularly interested in the views >>>>> of the regular developers, but also the wider community with interests >>>>> in the code. Perhaps an order of preference if you want, or FPTP; >>>>> but remember this is just a straw poll. >>>>> >>>>> Probably best to mail me direct, or via this list if you prefer. I >>>>> will tally and report. Got to do something while we wait for CVS to >>>>> return! >>>>> >>>>> I think I have decided my preference...... >>>>> >>>>> ==John ffitch >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel >>>>> Studio XE: >>>>> Pinpoint memory and threading errors before they happen. >>>>> Find and fix more than 250 security defects in the development cycle. >>>>> Locate bottlenecks in serial and parallel code that limit performance. >>>>> http://p.sf.net/sfu/intel-dev2devfeb >>>>> _______________________________________________ >>>>> Csound-devel mailing list >>>>> Csound-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>>> Pinpoint memory and threading errors before they happen. >>>> Find and fix more than 250 security defects in the development cycle. >>>> Locate bottlenecks in serial and parallel code that limit performance. >>>> http://p.sf.net/sfu/intel-dev2devfeb >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>> >>> >>> >>> >>> -- >>> >>> Saludos, >>> Felipe Sateler >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> -- >> Sent from my mobile device >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Michael Gogins Irreducible Productions http://www.michael-gogins.com Michael dot Gogins at gmail dot com ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2011-02-09 22:32
From	Oeyvind Brandtsegg
Subject	Re: [Cs-dev] DVCS again
	I would vote for Mercurial too, as it definately seems simpler to use, but it seems git might be more flexible so that's ok too. Oeyvind 2011/2/9 Steven Yi : > Mercurial for me, with git as a 2nd choice. > > On 2/9/11, Felipe Sateler wrote: >> Git would be my choice too. >> >> On Wed, Feb 9, 2011 at 15:27, Victor Lazzarini >> wrote: >>> I would vote for GIT. >>> Victor >>> On 9 Feb 2011, at 18:12, John ff wrote: >>> >>>> Following all the e-mails I have been convinced that we need to move >>>> to a DVCS while continuing to use SF as the central release point. >>>> This seems to mean one of >>>> >>>> GIT >>>> Mercurial >>>> Bazaar >>>> >>>> Can we have a straw poll? I am particularly interested in the views >>>> of the regular developers, but also the wider community with interests >>>> in the code. Perhaps an order of preference if you want, or FPTP; >>>> but remember this is just a straw poll. >>>> >>>> Probably best to mail me direct, or via this list if you prefer. I >>>> will tally and report. Got to do something while we wait for CVS to >>>> return! >>>> >>>> I think I have decided my preference...... >>>> >>>> ==John ffitch >>>> >>>> ------------------------------------------------------------------------------ >>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel >>>> Studio XE: >>>> Pinpoint memory and threading errors before they happen. >>>> Find and fix more than 250 security defects in the development cycle. >>>> Locate bottlenecks in serial and parallel code that limit performance. >>>> http://p.sf.net/sfu/intel-dev2devfeb >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> >> >> -- >> >> Saludos, >> Felipe Sateler >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > -- > Sent from my mobile device > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net