hg export tip -o filename.patch and send the patch to the maintainer. Or (which is a longer way), fork weblocks-dev on bitbucket, push your changes to that fork and let the maintainer know, so that he can pull your changes in. Also, a really simple intro to mercurial is here: http://www.selenic.com/mercurial/wiki/index.cgi/Tutorial
On 14 Mar, 22:36, Robin Lee Powell <[email protected]> wrote: > I don't understand mercurial or bitbucket, and I don't especially > *want* to; weblocks is the only project I'm on that uses them, so I > just want to know enough to be able to contribute. > > I'm about to do a bunch of work on the Weblocks Tinaa documentation. > What I'd *like* to do with the results is send a patch to the list, > but I gather that makes things hard. > > So, my question is this: > > I run clbuild install weblocks-dev, where "weblocks-dev" points > tohttp://www.bitbucket.org/S11001001/weblocks-dev/ > > I cd to the resulting source tree. > > I make my changes, and test them, and such. > > At that point, what is the easiest way for me to get those changes > to the commiters without making their life difficult? > > -Robin > > -- > They say: "The first AIs will be built by the military as weapons." > And I'm thinking: "Does it even occur to you to try for something > other than the default outcome?" > --http://shorl.com/tydruhedufogrehttp://www.digitalkingdom.org/~rlpowell/***http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
