Re: Large patches in git repositories

2012-10-17 Thread Michael Shigorin
On Wed, Oct 17, 2012 at 12:02:43PM +0300, Elan Ruusam??e wrote: > also question remains: why not just create new tarball? :) Might be interesting for those reading in Russian: http://www.altlinux.org/Руководство_по_gear (the article looks at several distinct types of package-in-git maintenance) P

Re: Large patches in git repositories

2012-10-17 Thread Elan Ruusamäe
On 17.10.2012 04:36, Kacper Kornet wrote: >with addtional change, that move them to distfiles when you're done Probably it would be best if it was done by developers updating given patch. As they now whether it contains PLD specific changes or not. imho in that case one should create two patche

Re: Large patches in git repositories

2012-10-16 Thread Kacper Kornet
On Tue, Oct 16, 2012 at 12:21:03AM +0300, Elan Ruusamäe wrote: > On 09/10/12 04:52, Kacper Kornet wrote: > >In my opinion a better idea is to keep in a package a script that > >generates the compressed patch,pushes it to dropin and updates > ># Patch-md5: > go on with this, and block huge patches f

Re: Large patches in git repositories

2012-10-15 Thread Elan Ruusamäe
On 09/10/12 04:52, Kacper Kornet wrote: In my opinion a better idea is to keep in a package a script that generates the compressed patch,pushes it to dropin and updates # Patch-md5: go on with this, and block huge patches from now on. if possible point to this mail thread as there are no actual

Re: Large patches in git repositories

2012-10-08 Thread Kacper Kornet
On Fri, Oct 05, 2012 at 05:59:42PM +0200, Paweł Sikora wrote: > On Friday 05 of October 2012 16:05:16 Kacper Kornet wrote: > > Recently one email to pld-cvs was blocked due to large size of generated > > diff. The "offending" file was gcc-branch.diff from crossmingw64-gcc > > which is 11M. > > Doe

Re: Large patches in git repositories

2012-10-05 Thread Paweł Sikora
On Friday 05 of October 2012 16:05:16 Kacper Kornet wrote: > Recently one email to pld-cvs was blocked due to large size of generated > diff. The "offending" file was gcc-branch.diff from crossmingw64-gcc > which is 11M. > > Does this file include and PLD specific changes or is it just a diff > be

Large patches in git repositories

2012-10-05 Thread Kacper Kornet
Recently one email to pld-cvs was blocked due to large size of generated diff. The "offending" file was gcc-branch.diff from crossmingw64-gcc which is 11M. Does this file include and PLD specific changes or is it just a diff between released version and tip of branch in some foreign (not PLD) repo