Re: How does team maintenace of python module works?
On 02/15/2013 05:21 PM, Dmitry Shachnev wrote:
> On Thu, Feb 14, 2013 at 10:54 PM, Thomas Goirand <zigo@debian.org> wrote:
>> I believe there's some misunderstanding, so I must make it square.
>> Again, I'm *not* asking for a full switch (or any switch at all) of all
>> (or even some) packages of the python module team. I have *NEVER*
>> written such thing, so could anyone writing in this tread refrain from
>> switching to this topic? If you do want to talk about it (which would be
>> a great move, IMO), do it in another thread, or at least not as a reply
>> to my message.
>
> I'm speaking about the same thing as you are. Having some packages is
> SVN and some in Git (it's what you mean) will make it harder to do
> mass-commits, mass-search and keeping up with others' changes.
>
> Again, I prefer Git to SVN, but I agree with Barry, Scott and others
> that divergence is *not* what we want.
>
> --
> Dmitry Shachnev
So, should I open a new Alioth group for maintaining Python modules
collectively using Git?
Thomas
Reply to: