Perl 6 - the future is here, just unevenly distributed

IRC log for #perl11, 2014-01-13

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

All times shown according to UTC.

Time Nick Message
02:17 bulk88 Will_the_Chill some bot lost ops, and so did I, re op as necessery
02:17 bulk88 Will_the_Chill_2 mst rurban ingy ^
02:20 bulk88 Bender1 was the op bot and he is gone
02:21 bulk88 "03[11:17] * Bender1 sets mode: +o Will_the_Chill
02:21 bulk88 [11:29] * @Bender1 (~Bender@agaton.scsys.co.uk) Quit (Remote host closed the connection)" and never came back
02:36 Will_the_Chill bulk88: I see my Will_the_Chill_2 user still has ops.  how do I re-op myself and you?  how do we get Bender back?
02:36 Bender joined #perl11
02:36 Will_the_Chill oh wow that seemed magical
02:37 Will_the_Chill was it enough to just say the word "Bender"?
02:37 perigrin bulk88: afaik ruban and ingy can't help there.
02:37 perigrin Will_the_Chill: almost magical :)
02:37 Will_the_Chill perigrin: was that a coincidence that as soon as I wrote my message you did something?
02:38 perigrin a bit yeah
02:39 perigrin I saw the activity and checked this channel
02:42 Will_the_Chill *nods head*
02:45 Will_the_Chill so you're the guy we bug when Bender disappears?
02:45 Will_the_Chill rurban: you back from the park yet?
03:14 rurban1 joined #perl11
03:15 perigrin Will_the_Chill: yeah
03:15 perigrin I'm the bender guy:0
03:15 perigrin er :)
03:50 Will_the_Chill perigrin: awesome, good to know, thanks my friend!  :)
03:50 perigrin np
04:06 rurban1 Will_the_Chill: I haven't touched gh-pages, just master
04:08 rurban1 It was you: 71bb7d67b1ed5ba added the wrong files to gh-pages
04:09 rurban1 joined #perl11
04:09 rurban1 Will: it was you. 71bb7d67b1ed5ba added the pm files to gh-pages
04:10 rurban1 joined #perl11
04:10 rurban1 Will: it was you. 71bb7d67b1ed5ba added the pm files to gh-pages
04:11 rurban1 Will: it was you. 71bb7d67b1ed5ba added the pm files to gh-pages
04:17 rurban1 oops, 4x times
04:17 rurban1 Will_the_Chill: I reverted your branch merge 3936eefaa which merged master with gh-pages
04:18 rurban1 manually. take care with branch merges (pull on wrong branches)
04:20 Will_the_Chill rurban1: okay I will look
04:22 Will_the_Chill rurban1: I am confused
04:22 Will_the_Chill (of course)
04:22 Will_the_Chill I am looking here: https://github.com/wbraswell/rperl/commit/3936eefaa
04:23 Will_the_Chill this was a trivial change a year ago?
04:23 Will_the_Chill how is it related to what we are seeing now?
04:24 rurban1 commit 3936eefaaf308d9dd37e29c1abceff2f19c67a91
04:24 rurban1 Merge: 71bb7d6 13a9191
04:24 rurban1 Author: Will Braswell <wbraswell@hush.com>
04:24 rurban1 Date:   Sun Jan 6 02:45:05 2013 -0600
04:24 rurban1 Merge branch 'master' of github.com:wbraswell/rperl
04:25 Will_the_Chill that can't be related to the gh-pages because I didn't even create the gh-pages until about 3 or 4 months ago
04:26 Will_the_Chill I see that what you did seems to have fixed things
04:26 rurban1 Wrong. this was the wrong merge: commit a19d8604d0f04cd3fefe88b5599d756c0917cbc5
04:26 rurban1 Merge: 9e6605d 3bf8f7f
04:26 rurban1 Author: Jonathan Mann <jmann@templateX-desktop.(none)>
04:26 rurban1 Date:   Tue Jan 7 19:05:09 2014 -0600
04:26 rurban1 Merge branch 'gh-pages' of https://github.com/wbraswell/rperl into gh-pages
04:26 Will_the_Chill YES there you go
04:26 Will_the_Chill okay thank you
04:27 rurban1 It could only be a branch merge. I named the wrong one
04:27 Will_the_Chill awesome!
04:27 Will_the_Chill I knew we could figure it out
04:27 Will_the_Chill or mostly YOU could figure it out, haha!
04:27 Will_the_Chill ;)
04:27 Will_the_Chill so what did you do to fix it?
04:27 rurban1 technically you could revert branch merges, but it is hairy. I just deleted the wrong src files.
04:28 Will_the_Chill what do you mean, "deleted the wrong src files"?
04:29 rurban1 git rm -r bla
04:29 rurban1 the revert would have been git revert -m 1 a19d8604d0f0
04:30 rurban1 -m 1 or -m 2
04:30 rurban1 http://git-scm.com/blog/2010/03/02/undoing-merges.html
04:31 Will_the_Chill yeah but why does rperl.org show the proper live file now (including your latest blog entry) when it did not show that before you did the manual delete?
04:31 bulk88 Bender trust bulk88
04:31 Bender bulk88, I already trust bulk88
04:31 bulk88 Bender trust bulk88_2
04:31 Bender OK, bulk88
04:32 Will_the_Chill Bender tell bulk88 you already trust him and not to be silly
04:32 rurban1 github needs a refresh on the gh-pages branch to recreate the files
04:32 Will_the_Chill I've never heard of a "branch refresh" before!
04:32 Will_the_Chill it always just did it automatically for me?
04:32 rurban1 it's documented somewhere on gh pages
04:33 Will_the_Chill I had jdmann84 use the same git commands as I used
04:33 rurban1 yes, any commit tp gh-pages drives a page refresh
04:33 rurban1 via a commit hook
04:33 Will_the_Chill well he did a commit to gh-pages because you could look at the github raw file and see the source had been updated
04:33 Will_the_Chill but rperl.org wasn't displaying it until you did whatever you just did
04:34 rurban1 maybe branch merges don't trigger the commit hook
04:34 Will_the_Chill OH it was because he did it wrong
04:34 Will_the_Chill gotcha
04:35 bulk88 "[21:36] * perigrin sets mode: +o bulk88" I wasn't sure if the bot  trusted me or not, that +0 will disappear on netsplit or sign/inout/
04:35 rurban1 Oh, you linked to me 1996 webpage, nice :)
04:35 rurban1 super up-to-date
04:35 Will_the_Chill rurban1: jdmann84 did that
04:35 Will_the_Chill I'm going to tell him to find a more up-to-date page
04:35 Will_the_Chill which do you prefer?
04:35 rurban1 I see :)
04:35 bulk88 perigrin was probably right that only he can control what rooms his op bot is in
04:35 rurban1 the blogs index probably
04:36 rurban1 http://blogs.perl.org/users/rurban/
04:36 rurban1 I can do it by myself also...
04:37 Will_the_Chill okay go for it
04:38 Will_the_Chill bulk88 trust Bender
04:38 * bulk88 already trusts Bender
04:39 Will_the_Chill yeah that's what I thought, but I wasn't sure
04:39 Will_the_Chill ;)
04:40 bulk88 WTC, im not sure your 2 separate branches with no ancestor is "safe" with git, I've heard Mercurial folks claiming that git "can't" have 2 branches with no connection, you obviously have it, but....
04:41 rurban1 somehow github adds an empty gh-pages branch, I guess.
04:41 rurban1 before your first commit
04:42 Will_the_Chill bulk88: it is built into github
04:42 Will_the_Chill I didn't invent it or even do it
04:42 Will_the_Chill github's system software magically does it
04:43 Will_the_Chill the gh-pages branch is magic
04:43 Will_the_Chill it is linked to your website
04:43 rurban1 There's an option when you create a new repo to initialize gh-pages somehow
04:43 bulk88 I'm just saying what the SO and slashdot grapevine has said about git vs mercurial, and with git you "need" separate .git dirs for  code bases that have no commonality, they might be quoting a very old version of git tho
04:44 rurban1 Typically a md only. any md file can be automatically converted into html by the gh-pages commit hook
04:45 rurban1 that is true about git. github does this seperation as seperates commit within the same .git
04:46 rurban1 on the other hand my wife is soo happy about http://www.huffingtonpost.com/2014/01/12/matthew-mcconaughey-best-actor_n_4562949.html finally getting the price he deserves (Golden Globe, best actor)
04:47 Will_the_Chill HAHA oh reini you so funny
04:47 Will_the_Chill are you sure you don't mean that YOU are the one who is soooo happy about McCconaughey?
04:47 Will_the_Chill ;)
04:47 rurban1 I dont care that much about him.
04:48 rurban1 But he was the best on this list by far. but not on my list
04:50 rurban1 She is swinging between him and J.Phoenix (Her) back and forth. A huge J.Phoenix poster is hanging next to her desk.
04:52 Will_the_Chill River Phoenix was a Boy Scout in Indiana Jones.  then he died.  :(
04:53 rurban1 And now I have to leave to check the NFL playoff results, if Payton Manning and Tom Brady lost in the first round…
04:53 rurban1 Oh good, both won.
04:55 Will_the_Chill haha football
04:55 Will_the_Chill I'm listening to Little Steven's Underground Garage, my favorite weekly radio show
05:00 bulk88 with "revert branch merge 3936eefaa which merged master with gh-pages" I think it didn't do what you think it did, the merge is still there
05:00 Will_the_Chill bulk88: see the recent history
05:00 bulk88 only a reset/rebase/force push will get rid of the merge
05:01 Will_the_Chill reini named the wrong merge as the culprit
05:01 Will_the_Chill and he didn't actually do an "un-merge"
05:01 Will_the_Chill he did a manual delete of the files that shouldn't have been in gh-pages branch
05:02 Will_the_Chill *recent chat history in this channel
05:02 Will_the_Chill rurban1: did you ever talk to shlomi on github to answer his question?
05:02 bulk88 but the git delete you did, didn't erase the mistake or fix the DAG
05:03 Will_the_Chill do y'all know shlomi?
05:03 Will_the_Chill bulk88: oh dang
05:03 Will_the_Chill bulk88: that's not good
05:03 Will_the_Chill can you show me what you mean?
05:04 bulk88 a git "revert" is a commit with the diff, reverting perfectly, another commit, a git reverse doesn't erase the mistake, it will be in the log forever
05:04 bulk88 it simply fixes your working tree to look normal/work again
05:05 bulk88 a git revert doesn't "rewrite history"
05:05 bulk88 ill get a pic in 3-10 mins of the problem i see
05:05 Will_the_Chill did reini do a git revert or something else?
05:05 Will_the_Chill I'm confused
05:05 bulk88 yes
05:17 bulk88 http://i44.tinypic.com/n1bkeu.png
05:19 bulk88 that 3936ee commit looks strange
05:19 Will_the_Chill okay it was my fault
05:19 bulk88 3936ee doesn't look like the merge commit at fault
05:19 Will_the_Chill bulk88: that's what I was telling you
05:19 Will_the_Chill 3936ee is unrelated
05:19 Will_the_Chill reini named the wrong merge as the culprit
05:20 Will_the_Chill it was my fault
05:20 bulk88 but on top of that, the merge is still in the log
05:20 Will_the_Chill yes we need to fix it
05:20 Will_the_Chill I don't know how to fix it, I need your help
05:20 Will_the_Chill we need to un-merge
05:20 bulk88 that is called cherrypick/rebase/force push/ and some other buzzwords
05:20 Will_the_Chill well the problem is I was using the jdmann84 account to help him get set up on a new laptop
05:21 Will_the_Chill and I must've done the wrong commands
05:21 Will_the_Chill and I must've messed it up
05:21 bulk88 and that is why i dont play with git's CLI
05:21 Will_the_Chill right
05:21 bulk88 reset is my favorite command in git
05:25 Will_the_Chill bulk88: if you can help, that would be great.  if not we might be stuck.
05:26 bulk88 Im going to try to delete those commits for practice and Ill put it on my repo of rperl if it still exists
05:26 Will_the_Chill cool beans
05:32 bulk88 http://i44.tinypic.com/30neq6e.jpg gh-pagesnew is the branch with the 2 commits removed
05:33 bulk88 I did a multi commit cherrypick by holding shift, highting all of them, then using mouse and control keys to deselect the 2 offending commits
05:33 Will_the_Chill interesting
05:33 Will_the_Chill well beyond my bit abilities at this point
05:33 Will_the_Chill *git abilities
05:34 bulk88 my git gui, when i did a rebase, it was forcing me to do a fast forward, which is NOT what I want to do, since that is requivelent of doing a reset to the HEAD commit of the remote, which has the problem commits in its history
05:34 bulk88 so instead I used the cherry pick tool
05:35 bulk88 im not sure what the difference is since the GUI window is 99% identical between the 2 modes
05:35 Will_the_Chill should I be worried by all this?
05:36 bulk88 im giving background info, no, because I was sucessful in deleting the 2 commits
05:36 Will_the_Chill cool
05:37 Will_the_Chill in that latest picture you linked, I see it is not sorted by date, I can't tell what it is sorted by?
05:37 bulk88 but notice, I "rewrote history", which some FOSS/git users say is a big no no, and can get to subject to e-violence
05:38 Will_the_Chill well it would be okay to "rewrite history" if me, the "boss guy" is the one who messed it up and needs help to fix it, yes?
05:38 Will_the_Chill as in, we're fixing a problem, not covering something up
05:38 bulk88 that pic was sorted by commit date
05:41 Will_the_Chill oh, right...  what's up with all the 1/13/2014 commit dates with old files?  my clock shows it as still being 1/12/2014 for another 20 minutes, so presumably those things from Jonathan Mann somehow got re-committed just now???
05:42 bulk88 " <@Will_the_Chill> well it would be okay to "rewrite history" if me, the "boss guy" is the one who messed it up and needs help to fix it, yes?" its your call, do you use emacs or vim? do you want to get roughed up and in a dumpster (but not dead)?
05:42 bulk88 my policy is, if it hasn't been published on cpan yet, you can rewrite history upto the last cpan release
05:43 bulk88 http://i44.tinypic.com/42n8m.png notice Commit Date and Commit Name colums are different
05:44 bulk88 I'm not sure how easy it is to fake the commit date and commiter name, of course it can be faked, but will I have to write a perl script that changes my system clock to do that?
05:44 Will_the_Chill I use vi(m) only.  :)
05:45 Will_the_Chill I agree with your policy for now as it seems reasonable enough
05:46 Will_the_Chill okay I see the commit name and author name columns are different, if that's what you were trying to show me on the latest pic
05:47 Will_the_Chill and also I feel bad for anyone who tries to "rough me up"
05:47 Will_the_Chill it would be a bad decision on their part
05:48 Will_the_Chill they might not survive, I'm just saying.  ;)
05:49 bulk88 " okay I see the commit name and author name columns are different, if that's what you were trying to show me on the latest pic" no, not that, look at "Commit Name" colum, on the commits between gh-pagesnew branch and wtcorigin/gh-pages branch
05:49 bulk88 http://i44.tinypic.com/42n8m.png in this pic
05:50 Will_the_Chill uh-huh, and the significant thing I'm taking away from the "commit name" column is that it is different than the "author name" column
05:50 Will_the_Chill oh sorry, just "author" not "author name" column
05:51 Will_the_Chill *different than ... between gh-pagesnew and wtcorgin/gh-pages
05:51 Will_the_Chill so yes, I think we're saying the same thing
05:51 Will_the_Chill WHICH IS TO SAY that it was your commit name "bulk88" that was responsible for the latest commits in the last few minutes, which is what I was asking about in the first place
05:53 bulk88 "commit name" is a different field from "author" in git, on P5P, because I dont have a commit bit, all of "my" commits to P5 have someone else under "commit name"
05:54 bulk88 the problem is git cherry pick isn't allowing enough forgery of what I want to do
05:56 bulk88 "--date=<date> " from https://www.kernel.org/pub/software/scm/git/docs/git-commit.html doesn't change commit date
05:56 bulk88 I'm pretty sure --date is only the "Date" column in that window
05:58 bulk88 what I could do is edit my .gitconfig so my name is Johnathan Mann, then do the cherry pick, then change my name to Reini Urban and do the last commit "improve Reini Urban homepage link and blogpost title"
05:58 bulk88 but that wont fix the commit date column
06:01 bulk88 git format patch, then apply patch didn't work either
06:01 bulk88 I need the Pirate Bay version of git
06:02 Will_the_Chill haha funny
06:02 Will_the_Chill is there actually a pirate bay version of git or is that a joke?
06:03 Will_the_Chill I don't see any reason why you would need to forge anything, it is okay if the names don't match, I actually see it a good thing because then we can see that you were the one who fixed it
06:04 bulk88 reading http://alexpeattie.com/blog/working-with-dates-in-git/  on how to force/forge  commit name and commit date
06:04 Will_the_Chill no don't force that stuff
06:04 Will_the_Chill just leave it
06:04 Will_the_Chill is there any reason why we MUST force it?
06:04 bulk88 "is there actually a pirate bay version of git or is that a joke?" no, but I wouldn't be surprised if I find that feature on a github fork somewhere
06:05 bulk88 "<@Will_the_Chill> is there any reason why we MUST force it?" only to make the "fix"/"rewriting" history even more untracable
06:05 Will_the_Chill no don't try to make it untraceable
06:05 rurban1 if there is no problem don't create one
06:05 Will_the_Chill bulk88: like I said it is okay to see that you were the one who fixed it
06:06 Will_the_Chill rurban1: bulk88 has a gui git tool that can do cherrypicking
06:07 Will_the_Chill I want to see that there was a problem, and that now it is fixed, and who was involved in fixing it
06:07 Will_the_Chill no forgery necessary AFAIU?
06:09 bulk88 "<@Will_the_Chill> I want to see that there was a problem, and that now it is fixed, and who was involved in fixing it" then I'll abandon trying to change those 2 columns and just deliver the change to github
06:10 bulk88 https://github.com/bulk88/rperl/commits/gh-pages upped
06:12 bulk88 http://i40.tinypic.com/1z1dzzm.png in the pic, b88origin is my repo, wtcorigin is your repo
06:12 bulk88 beige are remote branches
06:15 rurban1 nobody cares about gh-pages, I'm okay with a push -f. but then a revert -m1 would be better
06:15 Will_the_Chill rurban1: I care about gh-pages?  :)
06:16 Will_the_Chill bulk88: did you already upload it up to github?
06:17 bulk88 yes, its in my repo at https://github.com/bulk88/rperl/commits/gh-pages my master branch is very old, so dont fetch from it, only fetch from gh-pages on my repo, or ill delete my master branch if you want
06:18 bulk88 you will probably get a "can not fast forward" failure from git if you do a pull on my branch
06:18 bulk88 I think you have to do a pull with force, or a fetch, then reset to the head commit sha1 of my branch, both will give the same result
06:19 Will_the_Chill *sigh* I have no idea how to do any of that safely
06:19 bulk88 then, you will have to do a force push to overwrite the WTC github branch ofgh-pages
06:19 Will_the_Chill yeah I'm not gonna do that
06:19 Will_the_Chill just because I have no idea what I'm doing
06:19 Will_the_Chill which I've already proven by messing things up in the first place
06:20 Will_the_Chill I thought you could do the fix without my need of doing weird things
06:20 bulk88 if you do a "push" of your local gh-pages, which is my gh-pages, to your github repo, you will get an error that yoru local doesnt fast forward
06:20 bulk88 no, because without force, git will never "erase" any commits
06:20 bulk88 the whole crypto security idea
06:21 Will_the_Chill okay well it is starting to sound like a bad idea, relying on me to fix it
06:21 Will_the_Chill I'm just saying, I know my own limitations
06:21 Will_the_Chill and I'm a git newbie for sure
06:21 Will_the_Chill I don't want to hose things worse than I already have
06:21 bulk88 so force bypasses the safety rules and allows to write an entire new history to a remote or read a remote with a different history into your local
06:22 Will_the_Chill I understand what you're saying, force is an admin-only potentially-dangerous command
06:22 Will_the_Chill I'm cool with potentially dangerous unix commands, for instance
06:22 Will_the_Chill just not git  :/
06:23 bulk88 you could goto your github settings button, then collaborators tab, and give me commit access to your repo, ill do the force push, then you remove me, or someone else with commit access to your and knows more git than you can do it
06:24 bulk88 *to your repo
06:24 bulk88 urban and johnathan mann have it
06:25 bulk88 so does mst
06:25 Will_the_Chill you're already on the collaborators page!
06:25 Will_the_Chill https://github.com/wbraswell/rperl/settings/collaboration
06:25 bulk88 oh, IDK that
06:26 bulk88 want me to do the force push and make https://github.com/wbraswell/rperl/commits/gh-pages identical to https://github.com/bulk88/rperl/commits/gh-pages ?
06:27 rurban1 bulk88: your gh-pages do not look good.
06:28 bulk88 whats wrong?
06:28 rurban1 lemme check again…
06:29 rurban1 Oh, I see. looks good. Should I push it?
06:30 rurban1 pushed it :)
06:31 bulk88 rurban1, so youll take my gh-pages on github and force push it to WTC's gh-pages on github? if so, you are free to dit
06:31 rurban1 thanks for the work, bulk88
06:31 bulk88 saga over
06:31 Will_the_Chill I think it looks good???
06:31 Will_the_Chill saga over for reals?
06:31 Will_the_Chill how do I know?
06:31 rurban1 check it out
06:31 Will_the_Chill I FEEL SO HELPLESS!  hehehe
06:31 bulk88 https://github.com/wbraswell/rperl/commits/gh-pages
06:32 rurban1 My last commitmsg doesn't look good. feel free to fix it
06:32 bulk88 you can also click "network" on the right site and get a GUI line drawing of history like the ones my screenshots showed you
06:32 bulk88 *side
06:33 Will_the_Chill rurban1: how do we fix a commit message?
06:33 rurban1 g cia
06:34 rurban1 that's 3 aliases, commit —amend
06:34 rurban1 http://re-becca.org/ttrss/ ?? as referer
06:34 Will_the_Chill rurban1: I spent some time the other day trying to remember that you had created "ci" as an alias for "checkin" which is an alias for "commit"
06:34 Will_the_Chill *sigh*
06:34 bulk88 it will take a force push again, since your are rewriting history if the commit bacame public on github
06:35 rurban1 sure. but we already did it now
06:35 Will_the_Chill I think I'll skip it
06:36 bulk88 rurban1 https://github.com/wbraswell/rperl/commit/f3fad6e424c925d3dd90a6cc7519a9d702e49a04  i dont see the problem with this
06:36 Will_the_Chill we can have one sloppy commit message  :)
06:36 rurban1 There are my aliases: http://pastebin.com/tTdDdsPm
06:36 Will_the_Chill bulk88: I'm just very tidy and organized in my commit messages
06:37 Will_the_Chill rurban1: yes I looked in my own ~/.gitconfig file to see that you did have me put 'ci' alias in there
06:38 Will_the_Chill I was very confused and frustrated the other day when I couldn't get 'ci' to work on a different computer, haha!
06:38 rurban1 cia is for fixing the last commit
06:38 Will_the_Chill yes I've heard of amend I just haven't used it I guess
06:38 rurban1 that's one of the most common commands
06:39 Will_the_Chill *nods head*
06:39 Will_the_Chill I'm learning, slowly but surely
06:39 Will_the_Chill I thought I was so smart the other day, and look at where it got us!
06:40 Will_the_Chill I was setting up a new git for jdmann84 on his linux laptop
06:40 Will_the_Chill and that's how I hosed everything by using the jdmann84 account
06:40 bulk88 use git log [in a GUI], memory its keyboard shortcut [in a GUI]
06:41 bulk88 after every commit and before every git push git log it
06:41 Will_the_Chill git log?  is that a separate program from git itself?
06:41 rurban1 do a g s before a push (git show)
06:42 rurban1 log is the full list, show only for a single commit
06:48 Will_the_Chill so now I need to do the following commands on my laptop and jdmann84's laptop?
06:48 Will_the_Chill git checkout master
06:48 Will_the_Chill git pull origin master
06:48 Will_the_Chill git checkout gh-pages
06:48 Will_the_Chill git pull origin gh-pages
06:48 Will_the_Chill yes?
06:48 Will_the_Chill then my local copies will be aligned with the now-fixed github copies?
06:53 * bulk88 has no comment on the commands since he is afraid of lawsuits
06:53 Will_the_Chill well then rurban1 can comment
06:55 bulk88 http://paste.scsys.co.uk/290999
06:57 Will_the_Chill OH that's because github's magic saw that you had created a gh-pages branch, and looked for the magic CNAME file, and noticed it had my already-used rperl.org domian
06:57 Will_the_Chill *domain
06:57 Will_the_Chill nice to know that github has such internal error checking in place!  :)
07:14 rurban1 Will_the_Chill: git fetch; git co gh-pages; git reset —hard origin/gh-pages
07:15 rurban1 pull does a merge and you want to avoid this merge.
07:16 Will_the_Chill ah, I see, do not do a pull!
08:25 basiliscos joined #perl11
08:54 Will_the_Chill joined #perl11
14:32 bluescreen joined #perl11
15:56 rurban1 joined #perl11
18:36 mirjam joined #perl11
19:04 Will_the_Chill joined #perl11
21:57 bluescreen joined #perl11
22:14 sivoais joined #perl11
23:31 mirjam joined #perl11

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