Re: [Python-Dev] [Python-checkins] devguide (hg_transition): Update instructions to use the new "server-side clone" button
user: Antoine Pitrou <solipsis@pitrou.net> date: Tue Mar 01 20:51:42 2011 +0100 summary: Update instructions to use the new "server-side clone" button
That’s seriously awesome. Where can we have a look at the implementation? A remark: Having all clones created under a dedicated namespace (say sandbox) could make the hg.python.org listing clearer, since all user clones would be grouped. Some way to edit the clone description and contact would be great. Even without that, kudos for the excellent feature. Regards
On 01.03.2011 21:36, Éric Araujo wrote:
user: Antoine Pitrou <solipsis@pitrou.net> date: Tue Mar 01 20:51:42 2011 +0100 summary: Update instructions to use the new "server-side clone" button
That’s seriously awesome.
Where can we have a look at the implementation?
Have a guess :)
A remark: Having all clones created under a dedicated namespace (say sandbox) could make the hg.python.org listing clearer, since all user clones would be grouped.
Yes, but it also makes it harder to group by user.
Some way to edit the clone description and contact would be great.
Seconded. Georg
On Tue, 01 Mar 2011 21:36:29 +0100 Éric Araujo <merwok@netwok.org> wrote:
user: Antoine Pitrou <solipsis@pitrou.net> date: Tue Mar 01 20:51:42 2011 +0100 summary: Update instructions to use the new "server-side clone" button
That’s seriously awesome.
Where can we have a look at the implementation?
It's versioned on the server. I can send you a diff in private. I don't know how sensitive it might be, probably not unless there's some glaring security hole in it.
A remark: Having all clones created under a dedicated namespace (say sandbox) could make the hg.python.org listing clearer, since all user clones would be grouped.
Sure, we can change the enforced convention depending on the majority's preference. I chose that one because other devs thought it would be bad to let people create many repos at the top-level. Regards Antoine.
On Wed, Mar 2, 2011 at 6:54 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
A remark: Having all clones created under a dedicated namespace (say sandbox) could make the hg.python.org listing clearer, since all user clones would be grouped.
Sure, we can change the enforced convention depending on the majority's preference. I chose that one because other devs thought it would be bad to let people create many repos at the top-level.
Having user clones flagged by the two-level names should be more than enough when it comes to what the server enforces. That way we can be flexible about additional namespaces (although using "sandbox" by convention should cover most use cases). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (4)
-
Antoine Pitrou -
Georg Brandl -
Nick Coghlan -
Éric Araujo