!
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
decade of using Perl-style permissive
interpretations of version numbers:
https://bitbucket.org/pypa/pypi-metadata-formats/issues/41/how-much-compatability-is-enough#comment-10854105
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_
counts as prototyping and
research :)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea
hosting on GitHub, and then set up a Phabricator
instance for additional workflow flexibility:
https://www.python.org/dev/peps/pep-0481/
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general
the convenience of accepting changes online, while still keeping
the linear history on the main branch.
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
and manipulates the database directly:
https://git.beaker-project.org/cgit/beaker/tree/Server/bkr/server/tools/refresh_ldap.py),
but I expect something similar would likely work for Kallithea as
well.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
On 14 Mar 2015 22:42, Mads Kiilerich m...@kiilerich.com wrote:
On 03/14/2015 12:14 AM, Paul Nathan wrote:
Hallo,
I'd like to occasionally fix Kallithea bugs. I love the project and have
followed it for the past few years.
In order to do help out, I should (1) find bugs that are small
New issue 110: Investigate upgrading from Pylons to Pyramid
https://bitbucket.org/conservancy/kallithea/issue/110/investigate-upgrading-from-pylons-to
Nick Coghlan:
This isn't an urgent proposal, just a suggestion that an upgrade from Pylons to
Pyramid be considered at some point. At least from
to a specific
branch. However, while you could use named branches in hg, I'm not
sure what the equivalent would be in git (with the main problem being
how to decide which branch of an ancestral merge to follow)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
you can actually make use of
the role-based cross referencing capabilities.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http
cover in PEP 362
is the relatively manual process we currently use in CPython
development for adding public SSH keys to the authorized_keys file on
hg.python.org, so if Kallithea could help us automate that process as
well, it definitely adds to the case for adoption.
Regards,
Nick.
--
Nick
On 10 Feb 2015 04:33, Jan Heylen heyl...@gmail.com wrote:
On Mon, Feb 9, 2015 at 7:25 PM, Mads Kiilerich m...@kiilerich.com wrote:
I notice that PRs and comments pretty much corresponds to a 'forum'.
People
might have different policies for what they want to see, what they want
to
see
for these kinds of specific audience driven
capabilities without first checking that folks would be OK with my
doing that.
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
kallithea-general mailing list
kallithea-general
13 matches
Mail list logo