Hi Phreedom,
I could try solving it at the UI level, store the desired author in a
cookie... it's quite cumbersome nevertheless.
I was thinking the same thing. There already is a select box that contains
all known maintainers. It shouldn't be too hard to add another field where
people can
Hi,
On 13/01/14 15:53, Rob Vermaas wrote:
The Nixpkgs monitor server made by phreedom (Evgeny Egorochkin) has
moved to a new (easier to remember) URL:
http://monitor.nixos.org/
I have started using it already to update packages. It provides a nice
overview of packages that might have
On 01/14/2014 01:56 PM, Eelco Dolstra wrote:
Yes, thanks to Evgeny, this is very nice:-)
One comment: could we please set the Author field of commits to the person doing
the actual commit? Now we have all these unaccountable commits from Nixpkgs
Monitor none@none.
The committer is accounted,
On 01/14/2014 03:01 PM, Eelco Dolstra wrote:
But the committer is not shown in GitHub email messages, and tends to get lost
if you do things like cherry-picking into another branch, or commiting a pull
request from somebody else.
Github accounts for this author wrongly... it collects all with
Vladimír Čunát writes:
On 01/14/2014 03:01 PM, Eelco Dolstra wrote:
But the committer is not shown in GitHub email messages, and tends to get
lost
if you do things like cherry-picking into another branch, or commiting a pull
request from somebody else.
Github accounts for this author
On 01/14/2014 04:29 PM, Moritz Ulrich wrote:
The current approach looks correct to me: Nixpkgs-Monitor is the
original author of the patch, and applying this patch merely makes you
the committer, not the author.
Yes, it does seem consistent: author generated it and committer reviewed
it. When
On 01/14/2014 05:09 PM, Eelco Dolstra wrote:
Unless the commits are performed automatically by a daemon or something, it does
*not* make sense to set Author to Nixpkgs Monitor. I use all sorts of tools
to help me make patches (say nix-generate-from-cpan), but I don't put that in
the Author
On Tuesday, January 14, 2014 01:56:35 PM Eelco Dolstra wrote:
One comment: could we please set the Author field of commits to the person
doing the actual commit? Now we have all these unaccountable commits from
Nixpkgs Monitor none@none.
I could try solving it at the UI level, store the
Hi guys,
The Nixpkgs monitor server made by phreedom (Evgeny Egorochkin) has
moved to a new (easier to remember) URL:
http://monitor.nixos.org/
I have started using it already to update packages. It provides a nice
overview of packages that might have updates, you can download patches
for
I have seen these commits.
Is there anything we (maintainers) should do to get our packages
monitored? Some extra meta info to help discovery?
And thanks phreedom for creating this!
I think this will eventually save a lot of time for everyone.
Rob Vermaas rob.verm...@gmail.com writes:
Hi
FYI, the monitor appears to be down, i.e. any attempt to generate an
update patch fails with some kind of database error.
Take care,
Peter
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
On 01/13/2014 04:56 PM, Peter Simons wrote:
FYI, the monitor appears to be down, i.e. any attempt to generate an
update patch fails with some kind of database error.
I managed to generate some patches now, maybe just some cases are broken...
I find it a great tool... it even provides error
On Monday, January 13, 2014 04:53:37 PM Mathijs Kwik wrote:
I have seen these commits.
Is there anything we (maintainers) should do to get our packages
monitored? Some extra meta info to help discovery?
meta.repositories.git, meta.homepage. I'm currently testing the code that
leverages these
On Monday, January 13, 2014 04:56:08 PM Peter Simons wrote:
FYI, the monitor appears to be down, i.e. any attempt to generate an
update patch fails with some kind of database error.
Hopefully some kind of a fix fill be available once you report the specific
error ;)
Sqlite sometimes makes it
14 matches
Mail list logo
