Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2013-02-04

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
08:02 djun joined #webwork
08:25 djun joined #webwork
09:13 djun joined #webwork
15:01 aubreyja joined #webwork
15:17 rbeezer joined #webwork
15:54 goehle joined #webwork
18:27 djun joined #webwork
18:54 djun joined #webwork
19:30 djun joined #webwork
20:22 djun joined #webwork
21:23 aubreyja mgage: around?
21:55 mgage aubreyja: back from class
23:02 aubreyja hi - just wanted to extol the benefits of rebasing that I just learned today - it's very useful and I was able to replay all of my customizations on top of the ww2.5.1.3 branch
23:04 mgage yes -- I find it very useful as well -- you have to use it in the right way. Apparently you can cause a lot of trouble if you use it in the wrong way.
23:05 mgage I have some instructions at the bottom of the github page on the wiki that describes how a developer would use it on his local git repository -- see if it makes sense to you and if it is about what you did.
23:05 aubreyja that's what I read too - sure - I'll check it out.  I think it's a way to make sure you can do fast forward merges when people commit code too
23:06 mgage What it can do , which is good, is to make it look like your new features were all based on recent commit of the ongoing development branch.  Even though you actually checked out the branch months ago.
23:08 aubreyja And I used it to switch from webwork2 based code to webwork2-dev based code
23:09 mgage So rebasing rewrites your local branch to look as if you have done all of the feature development on the current version of the development code.  That makes it easier to merge back into the development
23:11 mgage Yes.  That works too.  What you don't want to do is to change any of the public master, devel or ww2.5.1.3 branches by rebasing them onto something else -- that changes their history in a way that means that everyone who has built on that code will have conflicts next time they try to update (pull) --- I think :-)
23:11 aubreyja right, I did that, pushed my mu-prod branch up to my github and now I just have to pull it down and do the actual switch.  It's very nice that I can easily run through the  exactupgrade on my laptop before pulling the trigger in production.
23:12 mgage yep -- although even then I've had to watch the production model carefully because the environment is often just slightly different.  But it sure helps.
23:12 mgage The ability to back out also going to be valuable once we figure out how to describe it simply.
23:15 mgage headed home.  ttyl
23:15 aubreyja btw, GatewayQuiz.pm is really in need of some love - the template is missing references to the new css and today I just fixed a bug in handling list answers...
23:16 aubreyja ttyl

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary