Good question, it looks like people on windows must do some configuration for line endings. TortoiseHg on Windows does not convert from unix line endings to windows or back (I tried it). Please see http://mercurial.selenic.com/wiki/Win32TextExtension for configuration. It looks like I should set up a repository hook that will block any commits that try to use Windows style newlines, to keep that from getting messy.
As far as patches go, hg has some features that help manage multiple patch sets but those look to be more of a maintainer's system rather than a contributor's system, something like diff -Naur mypyglet/ pyglet >foo.patch would still probably be the simplest way to generate a patch for submission. There's more about Mercurial's patch management here: http://hgbook.red-bean.com/read/managing-change-with-mercurial-queues.html -b On Jan 30, 12:54 am, claudio canepa <[email protected]> wrote: > On Fri, Jan 29, 2010 at 4:12 AM, Ben Smith > <[email protected]>wrote: > > > It appears that the migration from Subversion to Mercurial went well, > > though I had some network issues. Please let me know if you run in to > > any problems. > > > -b > > Just asking, the repo plays fair with line endings ? > People on windows must do something in their end to prevent problems with > line endings ? > I only recently begun to use hg, and the hgbook.red-bean was not so clear > about this. > Any instructions about how to generate a 'prefered' format for pyglet > patches ? > > -- > claudio -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
