Re: [suggest] rpmlint 0.92 take two
Hi, On 01/05/2010 04:25 PM, arnebjarn...@hotmail.com wrote: I have attached a new spec file and a new config.redhat (in the archive file). Unless the patch is exceptionally large ( eg: > 40KiB ) why not send it in a text attachment ? Significantly lowers the amount of effort required to look see. Just a question really. -- Karanbir Singh London, UK| http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc ___ suggest mailing list suggest@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/suggest
Re: [suggest] rpmlint 0.92 take two
Hi Karanbir. I am just used to zip/tar attachments, since I often see spam filters silent drop attachments other than compressed archive files. But I have no problems with sending diff patches uncomprssed if that is preferred by the RPMforge maintainers :-) Regards, Bjarne Unless the patch is exceptionally large ( eg: > 40KiB ) why not send it in a text attachment ? Significantly lowers the amount of effort required to look see. Just a question really. ___ suggest mailing list suggest@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/suggest
Re: [suggest] rpmlint 0.92 take two
On 01/05/2010 05:09 PM, arnebjarn...@hotmail.com wrote: I am just used to zip/tar attachments, since I often see spam filters silent drop attachments other than compressed archive files. But I have no problems with sending diff patches uncomprssed if that is preferred by the RPMforge maintainers :-) well, thats not me then! Since I dont have a single package in rpmforge :) Should and plan on changing that in the near future though. -- Karanbir Singh London, UK| http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc ___ suggest mailing list suggest@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/suggest
Re: [suggest] rpmlint 0.92 take two
On Tue, 5 Jan 2010, arnebjarn...@hotmail.com wrote: Unless the patch is exceptionally large ( eg: > 40KiB ) why not send it in a text attachment ? Significantly lowers the amount of effort required to look see. Just a question really. I am just used to zip/tar attachments, since I often see spam filters silent drop attachments other than compressed archive files. But I have no problems with sending diff patches uncomprssed if that is preferred by the RPMforge maintainers :-) I would prefer to have text be attached as-is. Not only because it simplifies my work, but rather because it lowers the barriere for other people to inspect and comment. I would be surprised if anyone looked inside the files now (by accident or on purpose ;-)). What would be even better, is commit access. Are you interested in committing your changes directly into RPMforge ? -- -- dag wieers, d...@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] ___ suggest mailing list suggest@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/suggest
