| Re: [proaudio] Status of pro-audio overlay and small updates |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] Status of pro-audio overlay and small updates
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Thu, 23 Aug 2012 19:33:33 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Thu, 23 Aug 2012 03:08:19 +0300,
keenblade <keenblade@xxxxxxxxx> a écrit :
> On Sal 21 Ağu 2012 23:56:03 EEST, Dominique Michel wrote:
>
> > "svn ci -m 'some comment'" look very easy and fast to me.
>
> I agree, it is easy and fast. I don't think forking will make easier
> things with git. But I am not against migrating to the git. Git is
> also easy and fast, too.
I know that, and I am not against migrating either. And tuxfamily do
have git and mercurial too. But, I want to have a good raison to
migrate. A migration imply work to do, that is time that will not be
used to make something else. And in many cases, a migration imply
also a loose of data like the historic.
And to have to manage send commits from other peoples is not what I
call a good raison. Again, I don't have the time for that.
For peoples not sure of their ebuilds, it is far better to make bug
reports with their ebuilds. That way, their ebuilds will be commented
and they will hopefully learn to make better ebuilds.
For peoples reasonably sure of their ebuilds, the best is when they get
commit access. And it will be the same problem in any case: for what
I know, only evermind and gimpel can give this access right to the
maintainers. But this is not so hard. When I begun as maintainer with
this overlay, we was 4 or 5 guys including gimpel and evermind. Today,
we are twenty with commit access to the svn. The last one is
nwmatt (Matt Henley), the guy that started this subject.
Welcome on board Matt! And thanks for helping!
>
> > Alternatively, he can send it to the list, but it will take more
> > time to do that than the above svn command.
> >
> > Dominique
> >
> Also people can use our bugtracker which is a better place to send
> patches, works or bug reports: http://proaudio.tuxfamily.org/bugs
That's right, even if I don't use it ofen. That way, they are also sure
they work will not be "lost" in the archive of this list.