[python-committers] branches and merging
Dirkjan Ochtman
dirkjan at ochtman.nl
Tue Mar 2 17:41:07 CET 2010
More information about the python-committers mailing list
Tue Mar 2 17:41:07 CET 2010
- Previous message: [python-committers] branches and merging
- Next message: [python-committers] branches and merging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Mar 2, 2010 at 17:12, Steve Holden <steve at holdenweb.com> wrote: > And does it look like a non-issue because you are familiar with the > Windows environment or because your imagination can't conceive of why it > would be a real problem? Does going ahead make development more > difficult for the Windows platform? I'm not fully familiar with the > issues, but if they were significant enough to persuade Brett that Hg > shouldn't go ahead I have to believe they are potential show-stoppers. It's perceived as not much of an issue, AFAICT, because people feel that using good editors will save you most of the time, pre-push hooks will prevent everyone from actually polluting the central repository, and it would be easy to install pre-commit hooks locally to get an early warning. ISTM that the remaining problem space is a high level of automation that some Windows developers desire, that they got from SVN, but that is quite small because there's a bunch of mitigating factors. It's perceived as a regression, and as making Windows developers second class because most of the issues won't come up on other systems. Cautiously formulating-ly, Dirkjan
- Previous message: [python-committers] branches and merging
- Next message: [python-committers] branches and merging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list