| 00:04.27 | *** join/#asterisk-dev babak (uid19622@gateway/web/irccloud.com/x-nqmpninldsryhzyv) |
| 00:17.56 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 00:26.51 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 00:28.13 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 00:47.19 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 00:51.11 | *** join/#asterisk-dev mjordan (~mjordan@75.76.55.191) |
| 00:51.11 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 00:57.16 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 02:32.56 | *** join/#asterisk-dev infobot (ibot@rikers.org) |
| 02:32.56 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Hell hath frozen over: Asterisk is moving to Git -=- Follow on Twitter at @AsteriskDev |
| 03:13.26 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 03:14.20 | *** part/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 05:15.41 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 05:57.41 | *** join/#asterisk-dev Demon_VoIP (~demon@109.60.135.186) |
| 06:45.30 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 07:08.16 | *** join/#asterisk-dev babak (uid19622@gateway/web/irccloud.com/x-yglcljbdfazfmjni) |
| 07:26.54 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:26.54 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 07:31.27 | *** join/#asterisk-dev doome (~doome@82.150.48.146) |
| 07:54.03 | *** join/#asterisk-dev pchero_work (~pchero@109.70.54.56) |
| 08:00.44 | *** join/#asterisk-dev doome (~doome@82.150.48.146) |
| 08:14.36 | *** join/#asterisk-dev skrusty (~skrusty@168.63.14.171) |
| 08:15.03 | *** join/#asterisk-dev pchero_work (~pchero@109.70.54.56) |
| 09:42.21 | stefan27 | how does Gerrit work? I tried to follow instructios on https://wiki.asterisk.org/wiki/display/AST/Gerrit+Usage but after checking out 'git clone -b 13 ssh://StefanEng86@gerrit.asterisk.org:29418/asterisk asterisk-13' and making the change i want, I cannot create a review-request with git review -t ASTERISK-24832 |
| 09:48.01 | coreyfarrell | stefan27: my guess is that you want: git review -t ASTERISK-24832 13 |
| 09:48.32 | coreyfarrell | by default it wants to post reviews against master, so for 13 you need to specify the target branch |
| 09:49.23 | stefan27 | Target branch?? |
| 09:49.49 | stefan27 | which branch of version 13? |
| 09:51.03 | coreyfarrell | 13 is the branch for version 13 |
| 09:54.21 | stefan27 | i cloned the repo as above, edited files, and tried to run 'git review -t ASTERISK-24832 13' but it said error you have unstaged changes |
| 09:55.04 | stefan27 | so i tried doing 'git stash' but that returned error 'fatal: git-write-tree: error building trees' and something about UPGRADE.txt needing merge |
| 09:55.57 | coreyfarrell | hmm, you might be in the middle of a failed rebase when when you tried running review without '13'.. does 'git status' tell you that you can run any commands with '--abort' ? |
| 09:56.47 | coreyfarrell | or does it just list what you did as 'Changes not staged for commit:' ? |
| 09:58.44 | stefan27 | Damn why is the output in Swedish... git status says (translated) "Not on any branch currently" then "changed by both UPGRADE.txt" then Untracked files "res/res_rtp_asterisk.c.orig" |
| 09:59.02 | stefan27 | i deleted the res_rtp_asterisk.c.orig |
| 10:00.30 | coreyfarrell | it doesn't say anything about running 'git rebase --abort'? |
| 10:00.38 | stefan27 | no nothing |
| 10:00.56 | stefan27 | ill link |
| 10:01.17 | stefan27 | http://pastebin.com/Cp6mWtjJ |
| 10:02.12 | stefan27 | Ej sammanslagna sökvägar ~ 'search paths not merged' Ospårade filer ~ 'untracked files' and inga ändringar... ~ 'no changes to check in' |
| 10:02.44 | stefan27 | How can i revert all my git operations and start over from scratch |
| 10:04.41 | stefan27 | these are all git-operations i have done including failures and typos http://pastebin.com/3gH2qx5E |
| 10:07.12 | coreyfarrell | so one thing that's interesting the first commit you do is with '--amend'. this seems wrong. |
| 10:07.53 | stefan27 | Yeah... |
| 10:08.52 | coreyfarrell | I'm not 100% sure on this but you could try 'git reset 13 --hard'. might be 'git reset origin/13 --hard' - I'm not sure since you amended the existing last commit. |
| 10:10.14 | stefan27 | HEAD är nu på b61c9a1 chan_pjsip: Fix crash during off-nominal when no endpoint specified. |
| 10:10.53 | coreyfarrell | so if you run 'git diff origin/13', it should say nothing? |
| 10:11.08 | stefan27 | Yes |
| 10:11.49 | coreyfarrell | so I think you're ready to try again :) |
| 10:12.29 | stefan27 | so i take old reviewboard patch patch -p0 < ../dtls.patch and rm res/res_rtp_asterisk.c.orig then just git stash followed by git review -t ASTERISK-24832 13 ? |
| 10:13.49 | coreyfarrell | no |
| 10:13.55 | coreyfarrell | git stash is not what you want.. |
| 10:14.48 | stefan27 | All i know of git is from looking at http://blog.interlinked.org/static/images/git/high-level-commands.png and reading a few minutes on wikipedia |
| 10:15.03 | coreyfarrell | apply the patch, cleanup the .orig file, then 'git add res/res_rtp_asterisk.c' and any other files you want to commit. then 'git commit' (with no --amend). |
| 10:15.47 | coreyfarrell | after you've committed the change, you can run 'git log', and it should show your change followed by "b61c9a1 chan_pjsip: Fix crash during off-nominal when no endpoint specified." |
| 10:16.03 | coreyfarrell | that's when you are ready to run 'git review -t ASTERISK-24832 13' |
| 10:16.37 | stefan27 | git commit outputted "You are not on any branch currently" |
| 10:16.52 | stefan27 | and "nothing to check in, working folder clean" |
| 10:17.05 | stefan27 | but i had done git add res/res_rtp_asterisk.c just before |
| 10:17.31 | coreyfarrell | you didn't 'git stash' right? |
| 10:18.20 | stefan27 | I did earlier just before you said 'git stash is not what you want' |
| 10:18.51 | stefan27 | Hmm my res/res_rtp_asterisk.c seems unpatched again |
| 10:19.03 | coreyfarrell | ok, so to undo that you would run 'git stash pop', but it's weird that it's saying you are not on any branch |
| 10:19.26 | coreyfarrell | 'git stash' clears all changes to the working copy, puts it into a stack. |
| 10:20.50 | stefan27 | now git commit worked without errors |
| 10:21.25 | coreyfarrell | ok, so 'git diff HEAD~1' shows your patch exactly? and 'git log' shows an entry for your change followed by the latest on 13? |
| 10:21.36 | stefan27 | but git review -t ASTERISK-24832 13 prompts me The outstanding commits are: 994782e (HEAD) ASTERISK-24832 |
| 10:21.36 | stefan27 | <PROTECTED> |
| 10:21.43 | stefan27 | Do you really want to submit the above commits? |
| 10:21.43 | stefan27 | Type 'yes' to confirm, other to cancel: |
| 10:21.58 | stefan27 | what is b61c9a1 (13) chan_pjsip: Fix crash during off-nominal when no endpoint specified. |
| 10:21.58 | stefan27 | <PROTECTED> |
| 10:22.45 | coreyfarrell | ok, the 'git reset 13 --hard' must not have quite done it. |
| 10:22.53 | stefan27 | <PROTECTED> |
| 10:23.24 | coreyfarrell | I think you've still touched the previous commit somehow, maybe it did nothing more than change the commit ID but that's enough. |
| 10:24.36 | stefan27 | btw there's no way I can destroy other people's work no matter what commands i write right? I don't have the rights? |
| 10:24.47 | coreyfarrell | so 'git reset 13 --hard' didn't go far enough back, you need 'git reset 13~1 --hard;git pull origin'. then reapply you're patch, 'git add' the files you changed, then git commit. |
| 10:25.19 | coreyfarrell | you can't destroy other peoples work on gerrit.asterisk.org, but you did mess up the local branch 13 when you amended the existing HEAD |
| 10:26.00 | coreyfarrell | also if the first line of your commit message was "ASTERISK-24832", you need to take a look at https://wiki.asterisk.org/wiki/display/AST/Commit+Messages |
| 10:26.11 | stefan27 | git reset 13~1 --hard;git pull origin outputted: HEAD är nu på dd78ab4 res_pjsip_config_wizard/config: Fix template processing |
| 10:26.11 | stefan27 | You asked to pull from the remote 'origin', but did not specify |
| 10:26.11 | stefan27 | a branch. Because this is not the default configured remote |
| 10:26.11 | stefan27 | for your current branch, you must specify a branch on the command line. |
| 10:26.37 | coreyfarrell | what about 'git checkout 13' ? |
| 10:27.23 | stefan27 | my branch and origin/13 has diverged |
| 10:27.40 | stefan27 | it suggests doing git pull |
| 10:27.43 | WIMPy | checkout -force? |
| 10:29.31 | stefan27 | same |
| 10:30.21 | coreyfarrell | I just did a 'git commit --amend' on one of my clean working copies, trying it out to see how to recover |
| 10:30.56 | stefan27 | jeez... all these because i wasn't allowed to paste the 5 lines of suggested change in the JIRA itself... On reviewboard i commented "Not in final form" meaning a developer should take a look at the code rather than accepting/rejecting the patch as is... |
| 10:31.00 | stefan27 | :) |
| 10:32.19 | stefan27 | But I guess me learning some git stuff can be useful to me also in some future |
| 10:32.40 | coreyfarrell | I was able to recover from "Your branch and 'origin/13' have diverged, and have 1 and 1 different commit each, respectively." by running: 'git reset HEAD~1 --hard;git pull origin' |
| 10:33.24 | stefan27 | Ok cool |
| 10:34.05 | coreyfarrell | this made my working copy go back to the previous commit (before the replacement commit I made when I did --amend), then 'git pull origin' brought the latest (un-amended) commit back into my working copy |
| 10:34.09 | stefan27 | but after I run git reset HEAD~1 --hard;git pull origin now. Then git diff HEAD~1 |
| 10:34.09 | stefan27 | <PROTECTED> |
| 10:34.32 | coreyfarrell | correct. you have to reapply your patch. |
| 10:35.25 | stefan27 | but i dont want to commit someone else's patch to pjsip in my push (git review request)? |
| 10:36.15 | stefan27 | now git diff HEAD~1 shows both the pjsip patch (not mine) and my dtls patch |
| 10:36.36 | coreyfarrell | don't worry about 'git diff HEAD~1' until you commit your patch. |
| 10:37.12 | stefan27 | so i repeat the git add and git commit now? |
| 10:37.19 | coreyfarrell | yes. |
| 10:38.22 | coreyfarrell | don't think of it as repeating though. it got messed up the first time and you started over. |
| 10:38.27 | stefan27 | How to edit /asterisk-13/.git/COMMIT_EDITMSG" to reference ASTERISK-24832 ? |
| 10:38.53 | stefan27 | https://wiki.asterisk.org/wiki/display/AST/Commit+Messages mentions: To have a commit noted in an issue, simply referencing the issue is sufficient: |
| 10:40.00 | stefan27 | but you say ASTERISK-24832 cannot be the only line i write? |
| 10:41.01 | coreyfarrell | you need to explain the change, only referencing the ticket is not enough (it'll never get approved that way). see https://wiki.asterisk.org/wiki/display/AST/Commit+Messages#CommitMessages-ExampleCommitMessage |
| 10:42.05 | stefan27 | Aha, I interpreted the "is sufficient" as "is sufficient for the entire commit msg" i guess i still need to mimic the example |
| 10:42.50 | stefan27 | The jira has information about reported by tested by and reason for change |
| 10:43.08 | stefan27 | I still *need* to duplicate that into the commit msg? |
| 10:43.38 | stefan27 | guess it can do no harm writing as in the example |
| 10:44.17 | coreyfarrell | stefan27: run 'git log'. imagine if this log said: ASTERISK-25086, ASTERISK-25089, ASTERISK-25090, ... |
| 10:50.34 | stefan27 | that wouldn't be cool i guess, but the person who looks at my particular patch should go to the jira as the single source of truth for the circumstances of the patch? |
| 10:51.23 | stefan27 | i put reported by and tested by in the git commit at least |
| 10:51.40 | coreyfarrell | no.. JIRA is more like a discussion that leads to the truth. the commit message should be the truth. |
| 10:52.01 | file | JIRA is the full history, the commit message is what happened as a result |
| 10:53.48 | stefan27 | Aha, but i imagined a developer would get the final word in my case; I only want to provide a patch for discussion |
| 10:54.47 | stefan27 | I was relayed to reviewboard after suggesting changes in the jira, now i was relayed to git :) |
| 10:57.50 | file | even for discussion an actual commit message is good, in case what you've done is correct and it can go into the tree |
| 10:58.06 | stefan27 | Okay i understand better now |
| 10:59.28 | file | looking back at reviewboard I only have one finding |
| 11:00.28 | file | potentially. |
| 11:04.23 | stefan27 | how do i edit the commit message after doing git commit and closing the generated file |
| 11:04.27 | stefan27 | before pushing |
| 11:04.39 | file | git commit --amend |
| 11:04.57 | stefan27 | thanks |
| 11:05.21 | file | achoo. |
| 11:21.13 | stefan27 | Oh the summary cannot be more than 80 characters? |
| 11:25.29 | stefan27 | ok so git review outputted * [new branch] HEAD -> refs/publish/13/ASTERISK-24832 |
| 11:25.47 | stefan27 | that's it? |
| 11:25.59 | file | yes |
| 11:26.09 | stefan27 | thanks for the git crash course |
| 11:26.15 | stefan27 | see you later |
| 12:07.47 | *** join/#asterisk-dev [TK]D-Fender (~chatzilla@216-191-106-163.dedicated.allstream.net) |
| 12:11.12 | tzafrir | stefan27, the summary should normally be less than 50 characters |
| 13:37.12 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 13:37.12 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 13:53.29 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 14:04.21 | *** join/#asterisk-dev putnopvut (putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:04.21 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 14:07.55 | *** join/#asterisk-dev sgriepentrog (sgriepentr@nat/digium/x-kyundlzpujojqncj) |
| 14:09.45 | *** join/#asterisk-dev mjordan (mjordan@nat/digium/x-qfqlgnpgusqsxmuw) |
| 14:09.45 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 14:28.34 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-xnfuzfmvaesphjnb) |
| 14:29.26 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-dvytjjauvvywcrsu) |
| 14:32.43 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 14:33.23 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-gulpojfydcwyrcpg) |
| 14:54.28 | *** join/#asterisk-dev Greenlight (wluke@cpc18-dund12-2-0-cust490.16-4.cable.virginm.net) |
| 15:03.45 | *** join/#asterisk-dev ipengineer (~zconkle@static-71-252-134-63.dllstx.fios.verizon.net) |
| 15:28.23 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 15:42.56 | *** join/#asterisk-dev newtonr (RustyNewto@nat/digium/x-gxsofqkosutpnvmk) |
| 15:42.56 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 15:51.04 | *** join/#asterisk-dev babak (uid19622@gateway/web/irccloud.com/x-aqvnmeyuqxbdystz) |
| 16:02.00 | file | superscrat, do you have additional findings on the mkrelease review? |
| 16:14.03 | *** join/#asterisk-dev [TK]D-Fender (~chatzilla@216-191-106-163.dedicated.allstream.net) |
| 16:35.36 | *** join/#asterisk-dev JunK-Y (~junky@pdpc/supporter/active/junk-y) |
| 16:40.05 | roramirez | Hi Guys! |
| 16:40.57 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 16:42.21 | roramirez | today is freeze of 14 version? |
| 16:42.31 | *** join/#asterisk-dev jameswf (uid27319@gateway/web/irccloud.com/x-mnrtswiqwrumbnrl) |
| 16:48.25 | file | nope |
| 16:48.26 | file | http://lists.digium.com/pipermail/asterisk-dev/2015-May/074910.html |
| 16:49.54 | roramirez | ok, thanks file |
| 18:04.21 | *** join/#asterisk-dev sgalarneau (Adium@nat/digium/x-mwzqxvguhdlvvsel) |
| 18:15.56 | *** join/#asterisk-dev ipengineer (~zconkle@static-71-252-134-63.dllstx.fios.verizon.net) |
| 18:41.00 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 18:58.43 | *** join/#asterisk-dev sgalarneau (Adium@nat/digium/x-ysmrrososdxqmydr) |
| 19:02.22 | *** join/#asterisk-dev sgalarneau (Adium@nat/digium/x-hqlzkvjsyqgjwpod) |
| 19:28.40 | *** join/#asterisk-dev y_ateya (~y_ateya@41.45.104.36) |
| 19:29.27 | coreyfarrell | file: ping from https://gerrit.asterisk.org/467 |
| 19:30.15 | file | ah, I did the other one |
| 19:30.36 | coreyfarrell | thank you :) |
| 19:32.06 | y_ateya | @rmudgett: Regarding deleting the assert in _ast_sched_del(), I really want to do this. But I think some people might not like it. |
| 19:32.52 | rmudgett | y_ateya: It should be done. |
| 19:33.51 | rmudgett | I'd replace it with a comment to not put another back there. |
| 19:34.22 | y_ateya | rmudgett: this is a good idea. |
| 19:38.48 | *** join/#asterisk-dev sgriepentrog (sgriepentr@nat/digium/x-czvnzpcnqjxrofhj) |
| 19:42.55 | *** join/#asterisk-dev wedhorn (~wedhorn@110-175-181-222.static.tpgi.com.au) |
| 19:54.43 | mjordan | gr. Spaces. |
| 19:54.51 | tensai | first time user of gerrit and I would appreciate some guidance |
| 19:55.07 | tensai | I submitted https://gerrit.asterisk.org/484 against master, and now added a cherry pick to 13 |
| 19:55.31 | tensai | but the patch to 11 is different. I've got that ready. can I link it to that review, or will it be independent? |
| 19:56.00 | mjordan | tensai: when you use git review, use the -t option to set the topic to ASTERISK-24887 |
| 19:56.25 | mjordan | that will "pull" the various reviews together. They won't be cherry-picks - because they aren't - but the same topic will cause them to be linked to each other in Gerrit |
| 19:56.50 | mjordan | The underlying JIRA issue will also look at the topic field to find which reviews apply to the issue |
| 19:56.58 | mjordan | Such that all of the various reviews will be linked to on that JIRA issue |
| 19:58.05 | *** join/#asterisk-dev Jacke (jacke@valhalla.bofh.org) |
| 20:03.15 | leifmadsen | mjordan, I'd consider some sort of gerrit review during astridevcon this year |
| 20:03.28 | leifmadsen | like a short "training" during the day |
| 20:04.15 | leifmadsen | I'd book no more than 20-30 mins for that, maybe lead with it into some discussion around Gerrit and how it's worked out or whatever? |
| 20:05.28 | file | if we could channel that into more documentation, sure |
| 20:09.28 | tensai | mjordan: trying that but I get an error that "git rebase -p -i remotes/gerrit/master" fails because "the previous cherry-pick is now empty" |
| 20:09.35 | tensai | is puzzled |
| 20:11.05 | file | what is the command you used to put it up for review? |
| 20:27.16 | tensai | git review -t ASTERISK-24887 |
| 20:27.21 | y_ateya | in chan_sip, I see that silenceSupp is not added to SDP by default; it is added only if ast_channel_timingfd is true. Is this a bug or feature? I think that it should be always added because asterisk don't support silence suppression. |
| 20:27.33 | mjordan | tensai: first, abandon the rebase it started for you |
| 20:27.47 | mjordan | tensai: when you post a patch for a branch that is *not* master, you have to specify which remote branch it is against |
| 20:27.57 | mjordan | tensai: so you'd want to use 'git review -t ASTERISK-24887 11' |
| 20:28.32 | tensai | got it |
| 20:31.24 | mjordan | y_ateya: could be construed either way. You are correct that Asterisk doesn't support silence suppression, however, whether or not that has to be explicitly conveyed in the SDP is questionable. It definitely *would never be able to* without a timing FD. |
| 20:31.31 | tensai | mjordan: I've got that posted now. So is there anything more I need to do, or is it all in your hands now? |
| 20:31.48 | mjordan | y_ateya: the absence of an attribute generally means that you are not negotiating that particular thing, so there's no real reason to always make it send it. |
| 20:32.07 | mjordan | tensai: well, not *my* hands specifically, it is in the hands of everyone :-) |
| 20:32.17 | mjordan | tensai: but yes, that's the only thing you have to do. |
| 20:32.23 | tensai | it was a collective "you" :) |
| 20:35.39 | putnopvut | file: I could use a bit of gerrit advice. I used 'git review -d' to get your res_sorcery_memory_cache changeset. I then added a commit to implement maximum_objects support. I want to somehow tell gerrit to push just my new commit up for review. Right now, I think if I try to run 'git review', I'll end up adding a new revision to your review and putting my commit up for review. Any idea how to make gerrit just add my new com |
| 20:35.39 | putnopvut | mit for review? |
| 20:36.40 | file | solid question, I don't know |
| 20:39.41 | file | actually... |
| 20:39.42 | file | try it |
| 20:39.45 | file | and see what happens |
| 20:40.19 | coreyfarrell | putnopvut: I'm pretty sure if the original commit doesn't get changed by you it won't update that review... otherwise it might cause that review to rebase. |
| 20:40.29 | file | yeah, that's what I'm thinking |
| 20:40.36 | file | the commit is the same |
| 20:40.36 | putnopvut | I'll give it a shot |
| 20:41.01 | *** join/#asterisk-dev y_ateya (~y_ateya@41.45.104.36) |
| 20:46.26 | y_ateya | does #asterisk-dev has a public log like #asterisk? I wanted to look some old messages but didn't find a log. |
| 20:46.43 | putnopvut | I think infobot logs stuff. |
| 20:47.40 | tensai | infobot: logs |
| 20:47.40 | infobot | All conversations are logged to http://infobot.rikers.org/%23asterisk%2ddev/ Lines starting with spaces are not logged. Logs are updated daily. |
| 20:56.12 | *** join/#asterisk-dev [TK]D-Fender (~joe@64.235.216.2) |
| 20:56.27 | coreyfarrell | While working on another patch I realized that logger.c never resets config [general] values to default during reload. if you load with 'exec_after_rotate=someutil', then delete that line and reload it will not clear the previous value. is this something that should be fixed in 11/13 or master only? |
| 20:57.31 | gtjoseph | coreyfarrell: how about 13/master? |
| 20:58.29 | coreyfarrell | gtjoseph: I don't see why it would be OK to put it in one released branch but not the other.. |
| 20:59.13 | gtjoseph | i lost track...is 11 still in normal bugfix mode? |
| 20:59.24 | coreyfarrell | yes |
| 20:59.32 | gtjoseph | ah |
| 20:59.47 | gtjoseph | then my vote'd be all 3 |
| 21:00.22 | coreyfarrell | 11 is full support for the next 17 months... |
| 21:00.51 | gtjoseph | i really lost track then :) |
| 21:01.18 | gtjoseph | i need a little post-it on my monitors |
| 21:05.11 | *** join/#asterisk-dev y_ateya (~y_ateya@41.45.104.36) |
| 21:15.56 | *** join/#asterisk-dev babak (uid19622@gateway/web/irccloud.com/x-seqbqkvcllszroas) |
| 22:25.50 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 22:44.43 | gtjoseph | file: got a sec for a dns question? |
| 22:44.53 | file | go for it |
| 22:45.06 | *** part/#asterisk-dev mjordan (mjordan@nat/digium/x-qfqlgnpgusqsxmuw) |
| 22:45.12 | gtjoseph | getting a lot of (DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)) messages lately... |
| 22:45.23 | gtjoseph | wondering what the current DNS path is in 13 |
| 22:45.37 | file | it uses the pjlib DNS client and pjsip DNS logic |
| 22:46.02 | gtjoseph | ok, i'll pursue there |
| 22:55.45 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 22:56.02 | gtjoseph | ah, we still configure the nameservers though. |
| 22:58.55 | file | yes |
| 23:17.41 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-gulpojfydcwyrcpg) |
| 23:39.24 | *** join/#asterisk-dev snuff-work (~blatus@203.87.61.22) |
| 23:39.24 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
