| Re: [proaudio] Git migration |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] Git migration
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Mon, 29 Jul 2013 18:48:43 +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 Mon, 29 Jul 2013 18:38:20 +0200,
Dominique Michel <dominique.michel@xxxxxxxxx> a écrit :
> Le Sun, 28 Jul 2013 22:06:14 +0200,
> Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
>
> > Hi all!
> >
> > Some time ago there was some discussion about whether the proaudio
> > overlay should migrate to git. Would it make sense to do such a
> > migration or would it be too much work for now?
> >
> > What are the arguments that support such a change? Furthermore, what
> > are the arguments against?
> >
> > One supportive argument is that pull requests or equivalent are
> > pretty nifty. On the contrary, SVN is (in my opinion) pretty nice
> > to work with, but that is not a strictly technical argument.
>
> I use both svn and git, and for a so simple project, the only
> "advantage" I can see with git is it is never. Which is not a
> technical argument either. We can now argue about the never, the
> better.
>
> And well, I use a test overlay for my personal ebuilds and to work on
> the pro-audio ebuilds. If I have 2 ebuilds with the same name, emerge
> will use the one in my test overlay, and I see no simpler way to do
> the same with a private git branch.
>
> Also, my test overlay include things that have nothing to do with the
> pro-audio overlay, so it is no point for me to include it in some
> private git branch.
>
> So well, I have no use for git with pro-audio, and I am just fine with
> svn.
But if someone can show he/she have an use case for a git repository in
the context of the overlay, I will have no objection to migrate.
>
> Also, the proaudio-dev branch can be used to put experimental or
> broken ebuilds, so that every body can look at them. For now, it is
> old stuffs in it, a real mess with no ChangeLog associated with the
> ebuilds, but nobody stop anyone to use it. It would be best to put
> ChangeLog files with new ebuilds here, with comments to explain what
> the issue is.
>
> Know someone what the ebuilds in proaudio-dev are? and if yes, can
> ChangeLog files be added. If not, we can purge all of them at the
> exception of 1 or 2 examples to show the file hierarchy. Or purge all
> of them and add a README.
>
> Dominique
>
> >
> > Thanks for your thoughts!
> >
> > Regards,
> > Karl
> >
> >
>
>
--
"We have the heroes we deserve."