From kde-panel-devel Sat May 04 07:12:06 2013 From: "Aaron J. Seigo" Date: Sat, 04 May 2013 07:12:06 +0000 To: kde-panel-devel Subject: Re: Plasma Workspaces 4.11: the last feature release in the 4.xseries for kde-workspace Message-Id: <4196159.aeaFoWPG4v () freedom> X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=136765159503324 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============3630171472203349284==" --===============3630171472203349284== Content-Type: multipart/signed; boundary="nextPart2244818.Mr7C8AMkUW"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart2244818.Mr7C8AMkUW Content-Type: multipart/alternative; boundary="nextPart2160758.Tpig8tY1mo" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart2160758.Tpig8tY1mo Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Friday, May 3, 2013 15:41:14 Michael Jansen wrote: > - Recommend forking them (gitorious, github, gko) for feature development Where was this said .. *anywhere*? Git has great support for branches; you can also merge and separate repositories nearly at will; creating new repositories is easy .. in the case of the secret service implementation there is no need to fork anything, especially not on some 3rd party infrastructure. > I somehow fail to grasp how recommending having n forks of those > repositories (one for each patch/feature) around makes work for packagers > and developers easier. I would also fail to grasp that recommendation. Thankfully, it isn't what I suggested, nor have I heard anyone else who is actually involved in any of these efforts say that. -- Aaron J. Seigo --nextPart2160758.Tpig8tY1mo Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

On Friday, May 3, 2013 15:41:14 Michael Jansen wrote:

> - Recommend forking them (gitorious, github, gko) for feature development

 

Where was this said .. *anywhere*? Git has great support for branches; you can also merge and separate repositories nearly at will; creating new repositories is easy .. in the case of the secret service implementation there is no need to fork anything, especially not on some 3rd party infrastructure.

 

> I somehow fail to grasp how recommending having n forks of those

> repositories (one for each patch/feature) around makes work for packagers

> and developers easier.

 

I would also fail to grasp that recommendation.

 

Thankfully, it isn't what I suggested, nor have I heard anyone else who is actually involved in any of these efforts say that.

 

--

Aaron J. Seigo

--nextPart2160758.Tpig8tY1mo-- --nextPart2244818.Mr7C8AMkUW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEABECAAYFAlGEtMoACgkQ1rcusafx20MqfACdGdHJbGlGNMzSZplG7HAEgXBa kWcAn2dFSq9hC4QJsSHmEnNO3JDrIV9a =jG0L -----END PGP SIGNATURE----- --nextPart2244818.Mr7C8AMkUW-- --===============3630171472203349284== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============3630171472203349284==--