On Fri, Jun 26, 2015 at 8:02 PM Eelco Dolstra eelco.dols...@logicblox.com
wrote:
BTW, this really should be in the Nixpkgs manual, not in some random
markdown file.
Actually, the file is not random, it is the one that GitHub suggests to
review when someone opens an issue or a pull-request
On Friday, June 26, 2015 16:55:43 Matthias Beyer wrote:
Hi,
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Someone fix this please, as I'm developing a script[0] which uses
monitor.nixos.org to
On 27-06-2015 16:24:01, phree...@yandex.ru wrote:
On Friday, June 26, 2015 16:55:43 Matthias Beyer wrote:
Hi,
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Someone fix this please, as I'm
Hi,
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Someone fix this please, as I'm developing a script[0] which uses
monitor.nixos.org to generate commits and I want to develop it even
further so one can
On 06/26/2015 04:55 PM, Matthias Beyer wrote:
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Maybe I missed something, but how does this new scheme looks like and
where was it announced?
signature.asc
On 26-06-2015 17:01:03, Pascal Wittmann wrote:
On 06/26/2015 04:55 PM, Matthias Beyer wrote:
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Maybe I missed something, but how does this new scheme looks
Hi,
On 26/06/15 17:30, Matthias Beyer wrote:
just wanted to report this: monitor.nixos.org generates patches which
do not fit the new scheme of how to name package update commits.
Maybe I missed something, but how does this new scheme looks like and
where was it announced?
