Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit :
> On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
> >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
> Given that the final git migration is imminent (really! otherwise I'm going to
> scream ;), can we not force people to go through this churn right now?

Indeed, I find that offensive : if git is a better tool than subversion, 
and if it's going to be used, what's the point?
> Yes, let's discourage any new packages from manually migrating or starting out
> in git just until flag day.  But I'm not sure it's worth removing DPMT on
> existing repos just to add it back, hopefully RSN.

I would like to make some points clear:
1. I wouldn't have contributed a single package in subversion, as it's just
too cumbersome to use. I liked svn when it replaced cvs, but not so much
since I started using git.
2. When I saw the DPMT policy mentioned only subversion, I asked around (can't
remember if it was just on IRC or on this ml) and was told it was ok to use
git since the migration was bound to happen sooner or later.
3. Afterwards, being just a DM, I sent RFS mails through this very list in
which I generally gave the Vcs-* fields from the d/control files, which
clearly showed I used git : no complaint about it.
4. Those package got sponsored without complaint about it either.

So you'll understand that getting flames (even with smileys) about it 
now is quite annoying.

I still have a series of things I plan to package for Debian ; those are 
Python Modules, and I'll use git. If that's a problem for the Debian 
Python Modules Team, can you point me to a more appropriate team?

Snark on #debian-python

Reply via email to