1,885
edits
Changes
Initial text
{|
|- id="t10:19:48"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: we have some students working on the 4.4 plugin stuff. thanks for your email.
|| [[#t10:19:48|10:19]]
|- id="t10:20:13"
! style="background-color: #407a40" | humph
| style="color: #407a40" | they are just trying to understand it all, which is turning out to be a good learning experience.
|| [[#t10:20:13|10:20]]
|- id="t10:22:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: great! it would be best if they work out of the 4.4 branch directly.
|| [[#t10:22:16|10:22]]
|- id="t10:22:36"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: once they have a patch against it, i can create a new svn branch in the FSF repo and apply it.
|| [[#t10:22:36|10:22]]
|- id="t10:22:54"
! style="background-color: #407a40" | humph
| style="color: #407a40" | can you say more about what you mean?
|| [[#t10:22:54|10:22]]
|- id="t10:23:02"
! style="background-color: #407a40" | humph
| style="color: #407a40" | like they should pull the 4.4 branch direct?
|| [[#t10:23:02|10:23]]
|- id="t10:24:59"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | right. checkout a 4.4 branch, apply the svn revisions i sent to it.
|| [[#t10:24:59|10:24]]
|- id="t10:25:04"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | hmm
|| [[#t10:25:04|10:25]]
|- id="t10:25:15"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | maybe it's easier for them if i create the sub-branch first.
|| [[#t10:25:15|10:25]]
|- id="t10:25:18"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | give me a minute.
|| [[#t10:25:18|10:25]]
|- id="t10:25:24"
! style="background-color: #407a40" | humph
| style="color: #407a40" | sure
|| [[#t10:25:24|10:25]]
|- id="t10:25:30"
! style="background-color: #407a40" | humph
| style="color: #407a40" | ctyler: ^^ fyi
|| [[#t10:25:30|10:25]]
|- id="t10:26:09"
| colspan="2" | * ctyler reads back
|| [[#t10:26:09|10:26]]
|- id="t10:26:17"
! style="background-color: #818144" | ctyler
| style="color: #818144" | howdy dnovillo
|| [[#t10:26:17|10:26]]
|- id="t10:26:18"
! style="background-color: #407a40" | humph
| style="color: #407a40" | this is one task where I dearly miss mercurial and svn falls down
|| [[#t10:26:18|10:26]]
|- id="t10:26:35"
! style="background-color: #407a40" | humph
| style="color: #407a40" | i.e., having to update to revisions to get changes and needing the network for that
|| [[#t10:26:35|10:26]]
|- id="t10:27:05"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: ctyler is a fedora guy, and also a prof with me (our students are both working on this)
|| [[#t10:27:05|10:27]]
|- id="t10:27:21"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: you can always work out of a git mirror off of the fsf, but in this case, doing it directly should also work.
|| [[#t10:27:21|10:27]]
|- id="t10:27:26"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ctyler: hi there.
|| [[#t10:27:26|10:27]]
|- id="t10:27:43"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: I'm just complaining :) We'll do it the svn way
|| [[#t10:27:43|10:27]]
|- id="t10:28:22"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ctyler: i'll create a branch of 4.4. so your students can put the patches in there. i don't think they'll need copyright assignments for this work, but let me check.
|| [[#t10:28:22|10:28]]
|- id="t10:28:40"
! style="background-color: #818144" | ctyler
| style="color: #818144" | ok, thanks.
|| [[#t10:28:40|10:28]]
|- id="t10:28:47"
! style="background-color: #818144" | ctyler
| style="color: #818144" | Borris should be joining us shortly.
|| [[#t10:28:47|10:28]]
|- id="t10:29:00"
! style="background-color: #407a40" | humph
| style="color: #407a40" | cool
|| [[#t10:29:00|10:29]]
|- id="t10:29:10"
! style="background-color: #407a40" | humph
| style="color: #407a40" | ehren's not around atm
|| [[#t10:29:10|10:29]]
|- id="t10:32:51"
| colspan="2" | * bchao (bchao@1FE5D3AD.33EE9F8A.1139E686.IP) has joined #static
|| [[#t10:32:51|10:32]]
|- id="t10:33:00"
| colspan="2" | * bchao is now known as BoChao
|| [[#t10:33:00|10:33]]
|- id="t10:33:10"
| colspan="2" | * ctyler sees massive netsplit on freenode
|| [[#t10:33:10|10:33]]
|- id="t10:33:40"
! style="background-color: #818144" | ctyler
| style="color: #818144" | dnovillo, meet BoChao, BoChao meet dnovillo
|| [[#t10:33:40|10:33]]
|- id="t10:33:52"
! style="background-color: #854685" | BoChao
| style="color: #854685" | hey dnovillo
|| [[#t10:33:52|10:33]]
|- id="t10:34:07"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: nice to meet you
|| [[#t10:34:07|10:34]]
|- id="t10:35:28"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: nice to meet you too
|| [[#t10:35:28|10:35]]
|- id="t10:37:17"
! style="background-color: #818144" | ctyler
| style="color: #818144" | BoChao: dnovillo is going to create a subversion branch for the 4.4 plugin backport
|| [[#t10:37:17|10:37]]
|- id="t10:37:33"
| colspan="2" | * ctyler has to step out for a few errands, will be back
|| [[#t10:37:33|10:37]]
|- id="t10:37:40"
! style="background-color: #854685" | BoChao
| style="color: #854685" | sounds good
|| [[#t10:37:40|10:37]]
|- id="t10:38:49"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ok, branch created.
|| [[#t10:38:49|10:38]]
|- id="t10:39:11"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | checkout the gcc-4_4-plugins branch with
|| [[#t10:39:11|10:39]]
|- id="t10:39:19"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: so what we'll do is swap out the 4.4.1 we had for this as our working base
|| [[#t10:39:19|10:39]]
|- id="t10:39:36"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:39:36|10:39]]
|- id="t10:40:46"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: do it over http:// instead of svn:// at school so you don't get throttled
|| [[#t10:40:46|10:40]]
|- id="t10:40:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | once you get that, apply the revisions i listed in my mail and send me the patch (Including the ChangeLog entries). I can then commit it back in the svn repository and everyone can then use a 4.4+plugins gcc
|| [[#t10:40:58|10:40]]
|- id="t10:43:29"
! style="background-color: #854685" | BoChao
| style="color: #854685" | humph: do I do a wget http://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:43:29|10:43]]
|- id="t10:43:31"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ?
|| [[#t10:43:31|10:43]]
|- id="t10:43:40"
! style="background-color: #407a40" | humph
| style="color: #407a40" | no, you can do it like he said
|| [[#t10:43:40|10:43]]
|- id="t10:43:47"
! style="background-color: #407a40" | humph
| style="color: #407a40" | but swap http:// for svn://
|| [[#t10:43:47|10:43]]
|- id="t10:44:02"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: just check out with svn directly. it will be easier for you to create a patch.
|| [[#t10:44:02|10:44]]
|- id="t10:44:40"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: one thing you may want to do is create a git repo for it once you check it out. or hg. whatever makes it easier for you to produce patches.
|| [[#t10:44:40|10:44]]
|- id="t10:45:14"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: I'm new to this :P
|| [[#t10:45:14|10:45]]
|- id="t10:46:05"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: that will probably make it easier then :). To apply patches from svn, you need to know the revision numbers.
|| [[#t10:46:05|10:46]]
|- id="t10:46:38"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so if you need to apply revision 13100, you just say
|| [[#t10:46:38|10:46]]
|- id="t10:46:47"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn diff -r 13099:13100
|| [[#t10:46:47|10:46]]
|- id="t10:46:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | that gives you the patch that introduced revision 13100
|| [[#t10:46:58|10:46]]
|- id="t10:47:17"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | you then apply that patch into your tree
|| [[#t10:47:17|10:47]]
|- id="t10:47:51"
! style="background-color: #854685" | BoChao
| style="color: #854685" | where would I enter that command?
|| [[#t10:47:51|10:47]]
|- id="t10:47:54"
! style="background-color: #854685" | BoChao
| style="color: #854685" | sorry for all the questions
|| [[#t10:47:54|10:47]]
|- id="t10:48:19"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: after you svn co you'll get a dir
|| [[#t10:48:19|10:48]]
|- id="t10:48:22"
! style="background-color: #407a40" | humph
| style="color: #407a40" | cd into that dir
|| [[#t10:48:22|10:48]]
|- id="t10:48:35"
! style="background-color: #407a40" | humph
| style="color: #407a40" | and you can run your other svn commands against that local working copy
|| [[#t10:48:35|10:48]]
|- id="t10:50:18"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ok
|| [[#t10:50:18|10:50]]
|- id="t10:50:28"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: right. so to get you started: 1- mkdir 44-plugins, 2- cd 44-plugins && svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:50:28|10:50]]
|- id="t10:51:08"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | that gives you a directory named gcc-4_4-plugins with the whole 4.4 gcc tree. It will take a while to download, we pile a lot of crap in there.
|| [[#t10:51:08|10:51]]
|- id="t10:51:21"
! style="background-color: #407a40" | humph
| style="color: #407a40" | :)
|| [[#t10:51:21|10:51]]
|- id="t10:51:53"
! style="background-color: #854685" | BoChao
| style="color: #854685" | yeah..its downloading
|| [[#t10:51:53|10:51]]
|- id="t10:52:03"
! style="background-color: #854685" | BoChao
| style="color: #854685" | but i didn't do step 1 :P
|| [[#t10:52:03|10:52]]
|- id="t10:52:10"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: if you do svn co svn://... vs. svn co http://... at school it will take *forever* as they have packet crap to foil you
|| [[#t10:52:10|10:52]]
|- id="t10:52:41"
! style="background-color: #854685" | BoChao
| style="color: #854685" | yeah...i switched that from your advice =)
|| [[#t10:52:41|10:52]]
|- id="t10:57:52"
! style="background-color: #854685" | BoChao
| style="color: #854685" | hmmm...i should have used screen
|| [[#t10:57:52|10:57]]
|- id="t10:58:33"
! style="background-color: #407a40" | humph
| style="color: #407a40" | never leave $HOME without it
|| [[#t10:58:33|10:58]]
|- id="t11:04:37"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: I just ran svn diff -r 13099:13100
|| [[#t11:04:37|11:04]]
|- id="t11:04:50"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: you will also need to checkout mainline. sorry i missed that.
|| [[#t11:04:50|11:04]]
|- id="t11:05:14"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | those rev #s i sent are against mainline. svn is not smart enough to get them if you're in a branch.
|| [[#t11:05:14|11:05]]
|- id="t11:05:34"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: what's your email address? i've got a little script that may help getting these revisions out.
|| [[#t11:05:34|11:05]]
|- id="t11:05:44"
! style="background-color: #854685" | BoChao
| style="color: #854685" | bchao@learn.senecac.on.ca
|| [[#t11:05:44|11:05]]
|- id="t11:06:43"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: great. actually, maybe easier to post the link http://airs.com/dnovillo/svn-get-rev
|| [[#t11:06:43|11:06]]
|- id="t11:06:57"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | do this:
|| [[#t11:06:57|11:06]]
|- id="t11:07:08"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn co svn://gcc.gnu.org/svn/gcc/trunk
|| [[#t11:07:08|11:07]]
|- id="t11:07:11"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ cd trunk
|| [[#t11:07:11|11:07]]
|- id="t11:07:18"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn-get-rev 146274
|| [[#t11:07:18|11:07]]
|- id="t11:07:35"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | it should output to stdout the log message for rev 146274 and the patch.
|| [[#t11:07:35|11:07]]
|- id="t11:07:59"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | do that for all the revisions i mailed and that should give you an aggregate patch that can then be retrofitted in the 4_4-plugin branch.
|| [[#t11:07:59|11:07]]
|- id="t11:08:39"
! style="background-color: #854685" | BoChao
| style="color: #854685" | so that script from that link, I run that in the gcc-4.4-plugin directory right?
|| [[#t11:08:39|11:08]]
|- id="t11:09:32"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: all svn commands should be run inside the working directory (i.e., what you checked out with svn co)
|| [[#t11:09:32|11:09]]
|- id="t11:10:32"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: no, the script svn-get-rev needs to be run inside your copy of 'trunk' because those revision numbers are against trunk.
|| [[#t11:10:32|11:10]]
|- id="t11:10:47"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | if you run svn-get-rev with those numbers inside the 4_4-plugin tree, you'll get an empty output.
|| [[#t11:10:47|11:10]]
|- id="t11:10:56"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ok
|| [[#t11:10:56|11:10]]
|- id="t11:12:35"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so, you'll have two gcc trees checked out. trunk and gcc-4_4-plugin.
|| [[#t11:12:35|11:12]]
|- id="t11:23:29"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph/ctyler/BoChao: i'm sending the announcement about the branch + rules for it. Are you all subscribed to gcc@gcc.gnu.org?
|| [[#t11:23:29|11:23]]
|- id="t11:24:03"
! style="background-color: #407a40" | humph
| style="color: #407a40" | I am not, no
|| [[#t11:24:03|11:24]]
|- id="t11:27:12"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | not really necessary, you can track it from the archives. the announcement won't say anything you don't already know.
|| [[#t11:27:12|11:27]]
|- id="t11:27:39"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | the one rule i'm imposing on the branch is that it will only accept backports from mainline. i don't want it to become a sandbox for new functionality.
|| [[#t11:27:39|11:27]]
|- id="t11:28:03"
! style="background-color: #407a40" | humph
| style="color: #407a40" | seems reasonable
|| [[#t11:28:03|11:28]]
|- id="t11:30:09"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: patches for this branch should be posted to gcc-patches@gcc.gnu.org and include the tag [44-plugins] in the Subject.
|| [[#t11:30:09|11:30]]
|- id="t11:33:50"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: i am not subscribed gcc@gcc.gnu.org
|| [[#t11:33:50|11:33]]
|- id="t11:34:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: this is an excellent time to subscribe. tune your filters, though.
|| [[#t11:34:16|11:34]]
|- id="t11:34:37"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | gcc@ is for discussions on development, gcc-patches@ is where we post all patches.
|| [[#t11:34:37|11:34]]
|- id="t11:35:06"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | we're cavemen and don't believe in tracking patches via modern ways.
|| [[#t11:35:06|11:35]]
|- id="t11:35:46"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: how do i subscribe?
|| [[#t11:35:46|11:35]]
|- id="t11:35:55"
! style="background-color: #407a40" | humph
| style="color: #407a40" | the thing about getting students involved, is that they have no habits to break, so whatever you do is what they become accustomed to doing
|| [[#t11:35:55|11:35]]
|- id="t11:36:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: http://gcc.gnu.org/lists.html choose gcc-patches and gcc.
|| [[#t11:36:16|11:36]]
|- id="t11:36:20"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: haha
|| [[#t11:36:20|11:36]]
|- id="t11:36:45"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: what is teh argumetn I need to type in for the script
|| [[#t11:36:45|11:36]]
|- id="t11:36:48"
! style="background-color: #854685" | BoChao
| style="color: #854685" | usage: svn-get-rev rev
|| [[#t11:36:48|11:36]]
|- id="t11:37:06"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | 'rev' is the number. those are the revision numbers i sent in my email.
|| [[#t11:37:06|11:37]]
|- id="t11:37:34"
! style="background-color: #854685" | BoChao
| style="color: #854685" | oh..ok, just type in those numbers in 1 by 1?
|| [[#t11:37:34|11:37]]
|- id="t11:37:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | yup. i would try to apply 1 patch at a time.
|| [[#t11:37:58|11:37]]
|- id="t11:38:22"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | in theory, the groups of revisions i sent should give you a buildable compiler every time.
|| [[#t11:38:22|11:38]]
|- id="t11:38:39"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so, apply the first group of revs. check that the compiler builds. then apply the second, etc.
|| [[#t11:38:39|11:38]]
|}
|- id="t10:19:48"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: we have some students working on the 4.4 plugin stuff. thanks for your email.
|| [[#t10:19:48|10:19]]
|- id="t10:20:13"
! style="background-color: #407a40" | humph
| style="color: #407a40" | they are just trying to understand it all, which is turning out to be a good learning experience.
|| [[#t10:20:13|10:20]]
|- id="t10:22:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: great! it would be best if they work out of the 4.4 branch directly.
|| [[#t10:22:16|10:22]]
|- id="t10:22:36"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: once they have a patch against it, i can create a new svn branch in the FSF repo and apply it.
|| [[#t10:22:36|10:22]]
|- id="t10:22:54"
! style="background-color: #407a40" | humph
| style="color: #407a40" | can you say more about what you mean?
|| [[#t10:22:54|10:22]]
|- id="t10:23:02"
! style="background-color: #407a40" | humph
| style="color: #407a40" | like they should pull the 4.4 branch direct?
|| [[#t10:23:02|10:23]]
|- id="t10:24:59"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | right. checkout a 4.4 branch, apply the svn revisions i sent to it.
|| [[#t10:24:59|10:24]]
|- id="t10:25:04"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | hmm
|| [[#t10:25:04|10:25]]
|- id="t10:25:15"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | maybe it's easier for them if i create the sub-branch first.
|| [[#t10:25:15|10:25]]
|- id="t10:25:18"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | give me a minute.
|| [[#t10:25:18|10:25]]
|- id="t10:25:24"
! style="background-color: #407a40" | humph
| style="color: #407a40" | sure
|| [[#t10:25:24|10:25]]
|- id="t10:25:30"
! style="background-color: #407a40" | humph
| style="color: #407a40" | ctyler: ^^ fyi
|| [[#t10:25:30|10:25]]
|- id="t10:26:09"
| colspan="2" | * ctyler reads back
|| [[#t10:26:09|10:26]]
|- id="t10:26:17"
! style="background-color: #818144" | ctyler
| style="color: #818144" | howdy dnovillo
|| [[#t10:26:17|10:26]]
|- id="t10:26:18"
! style="background-color: #407a40" | humph
| style="color: #407a40" | this is one task where I dearly miss mercurial and svn falls down
|| [[#t10:26:18|10:26]]
|- id="t10:26:35"
! style="background-color: #407a40" | humph
| style="color: #407a40" | i.e., having to update to revisions to get changes and needing the network for that
|| [[#t10:26:35|10:26]]
|- id="t10:27:05"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: ctyler is a fedora guy, and also a prof with me (our students are both working on this)
|| [[#t10:27:05|10:27]]
|- id="t10:27:21"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: you can always work out of a git mirror off of the fsf, but in this case, doing it directly should also work.
|| [[#t10:27:21|10:27]]
|- id="t10:27:26"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ctyler: hi there.
|| [[#t10:27:26|10:27]]
|- id="t10:27:43"
! style="background-color: #407a40" | humph
| style="color: #407a40" | dnovillo: I'm just complaining :) We'll do it the svn way
|| [[#t10:27:43|10:27]]
|- id="t10:28:22"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ctyler: i'll create a branch of 4.4. so your students can put the patches in there. i don't think they'll need copyright assignments for this work, but let me check.
|| [[#t10:28:22|10:28]]
|- id="t10:28:40"
! style="background-color: #818144" | ctyler
| style="color: #818144" | ok, thanks.
|| [[#t10:28:40|10:28]]
|- id="t10:28:47"
! style="background-color: #818144" | ctyler
| style="color: #818144" | Borris should be joining us shortly.
|| [[#t10:28:47|10:28]]
|- id="t10:29:00"
! style="background-color: #407a40" | humph
| style="color: #407a40" | cool
|| [[#t10:29:00|10:29]]
|- id="t10:29:10"
! style="background-color: #407a40" | humph
| style="color: #407a40" | ehren's not around atm
|| [[#t10:29:10|10:29]]
|- id="t10:32:51"
| colspan="2" | * bchao (bchao@1FE5D3AD.33EE9F8A.1139E686.IP) has joined #static
|| [[#t10:32:51|10:32]]
|- id="t10:33:00"
| colspan="2" | * bchao is now known as BoChao
|| [[#t10:33:00|10:33]]
|- id="t10:33:10"
| colspan="2" | * ctyler sees massive netsplit on freenode
|| [[#t10:33:10|10:33]]
|- id="t10:33:40"
! style="background-color: #818144" | ctyler
| style="color: #818144" | dnovillo, meet BoChao, BoChao meet dnovillo
|| [[#t10:33:40|10:33]]
|- id="t10:33:52"
! style="background-color: #854685" | BoChao
| style="color: #854685" | hey dnovillo
|| [[#t10:33:52|10:33]]
|- id="t10:34:07"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: nice to meet you
|| [[#t10:34:07|10:34]]
|- id="t10:35:28"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: nice to meet you too
|| [[#t10:35:28|10:35]]
|- id="t10:37:17"
! style="background-color: #818144" | ctyler
| style="color: #818144" | BoChao: dnovillo is going to create a subversion branch for the 4.4 plugin backport
|| [[#t10:37:17|10:37]]
|- id="t10:37:33"
| colspan="2" | * ctyler has to step out for a few errands, will be back
|| [[#t10:37:33|10:37]]
|- id="t10:37:40"
! style="background-color: #854685" | BoChao
| style="color: #854685" | sounds good
|| [[#t10:37:40|10:37]]
|- id="t10:38:49"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | ok, branch created.
|| [[#t10:38:49|10:38]]
|- id="t10:39:11"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | checkout the gcc-4_4-plugins branch with
|| [[#t10:39:11|10:39]]
|- id="t10:39:19"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: so what we'll do is swap out the 4.4.1 we had for this as our working base
|| [[#t10:39:19|10:39]]
|- id="t10:39:36"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:39:36|10:39]]
|- id="t10:40:46"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: do it over http:// instead of svn:// at school so you don't get throttled
|| [[#t10:40:46|10:40]]
|- id="t10:40:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | once you get that, apply the revisions i listed in my mail and send me the patch (Including the ChangeLog entries). I can then commit it back in the svn repository and everyone can then use a 4.4+plugins gcc
|| [[#t10:40:58|10:40]]
|- id="t10:43:29"
! style="background-color: #854685" | BoChao
| style="color: #854685" | humph: do I do a wget http://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:43:29|10:43]]
|- id="t10:43:31"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ?
|| [[#t10:43:31|10:43]]
|- id="t10:43:40"
! style="background-color: #407a40" | humph
| style="color: #407a40" | no, you can do it like he said
|| [[#t10:43:40|10:43]]
|- id="t10:43:47"
! style="background-color: #407a40" | humph
| style="color: #407a40" | but swap http:// for svn://
|| [[#t10:43:47|10:43]]
|- id="t10:44:02"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: just check out with svn directly. it will be easier for you to create a patch.
|| [[#t10:44:02|10:44]]
|- id="t10:44:40"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: one thing you may want to do is create a git repo for it once you check it out. or hg. whatever makes it easier for you to produce patches.
|| [[#t10:44:40|10:44]]
|- id="t10:45:14"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: I'm new to this :P
|| [[#t10:45:14|10:45]]
|- id="t10:46:05"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: that will probably make it easier then :). To apply patches from svn, you need to know the revision numbers.
|| [[#t10:46:05|10:46]]
|- id="t10:46:38"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so if you need to apply revision 13100, you just say
|| [[#t10:46:38|10:46]]
|- id="t10:46:47"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn diff -r 13099:13100
|| [[#t10:46:47|10:46]]
|- id="t10:46:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | that gives you the patch that introduced revision 13100
|| [[#t10:46:58|10:46]]
|- id="t10:47:17"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | you then apply that patch into your tree
|| [[#t10:47:17|10:47]]
|- id="t10:47:51"
! style="background-color: #854685" | BoChao
| style="color: #854685" | where would I enter that command?
|| [[#t10:47:51|10:47]]
|- id="t10:47:54"
! style="background-color: #854685" | BoChao
| style="color: #854685" | sorry for all the questions
|| [[#t10:47:54|10:47]]
|- id="t10:48:19"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: after you svn co you'll get a dir
|| [[#t10:48:19|10:48]]
|- id="t10:48:22"
! style="background-color: #407a40" | humph
| style="color: #407a40" | cd into that dir
|| [[#t10:48:22|10:48]]
|- id="t10:48:35"
! style="background-color: #407a40" | humph
| style="color: #407a40" | and you can run your other svn commands against that local working copy
|| [[#t10:48:35|10:48]]
|- id="t10:50:18"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ok
|| [[#t10:50:18|10:50]]
|- id="t10:50:28"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: right. so to get you started: 1- mkdir 44-plugins, 2- cd 44-plugins && svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_4-plugins
|| [[#t10:50:28|10:50]]
|- id="t10:51:08"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | that gives you a directory named gcc-4_4-plugins with the whole 4.4 gcc tree. It will take a while to download, we pile a lot of crap in there.
|| [[#t10:51:08|10:51]]
|- id="t10:51:21"
! style="background-color: #407a40" | humph
| style="color: #407a40" | :)
|| [[#t10:51:21|10:51]]
|- id="t10:51:53"
! style="background-color: #854685" | BoChao
| style="color: #854685" | yeah..its downloading
|| [[#t10:51:53|10:51]]
|- id="t10:52:03"
! style="background-color: #854685" | BoChao
| style="color: #854685" | but i didn't do step 1 :P
|| [[#t10:52:03|10:52]]
|- id="t10:52:10"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: if you do svn co svn://... vs. svn co http://... at school it will take *forever* as they have packet crap to foil you
|| [[#t10:52:10|10:52]]
|- id="t10:52:41"
! style="background-color: #854685" | BoChao
| style="color: #854685" | yeah...i switched that from your advice =)
|| [[#t10:52:41|10:52]]
|- id="t10:57:52"
! style="background-color: #854685" | BoChao
| style="color: #854685" | hmmm...i should have used screen
|| [[#t10:57:52|10:57]]
|- id="t10:58:33"
! style="background-color: #407a40" | humph
| style="color: #407a40" | never leave $HOME without it
|| [[#t10:58:33|10:58]]
|- id="t11:04:37"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: I just ran svn diff -r 13099:13100
|| [[#t11:04:37|11:04]]
|- id="t11:04:50"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: you will also need to checkout mainline. sorry i missed that.
|| [[#t11:04:50|11:04]]
|- id="t11:05:14"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | those rev #s i sent are against mainline. svn is not smart enough to get them if you're in a branch.
|| [[#t11:05:14|11:05]]
|- id="t11:05:34"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: what's your email address? i've got a little script that may help getting these revisions out.
|| [[#t11:05:34|11:05]]
|- id="t11:05:44"
! style="background-color: #854685" | BoChao
| style="color: #854685" | bchao@learn.senecac.on.ca
|| [[#t11:05:44|11:05]]
|- id="t11:06:43"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: great. actually, maybe easier to post the link http://airs.com/dnovillo/svn-get-rev
|| [[#t11:06:43|11:06]]
|- id="t11:06:57"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | do this:
|| [[#t11:06:57|11:06]]
|- id="t11:07:08"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn co svn://gcc.gnu.org/svn/gcc/trunk
|| [[#t11:07:08|11:07]]
|- id="t11:07:11"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ cd trunk
|| [[#t11:07:11|11:07]]
|- id="t11:07:18"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | $ svn-get-rev 146274
|| [[#t11:07:18|11:07]]
|- id="t11:07:35"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | it should output to stdout the log message for rev 146274 and the patch.
|| [[#t11:07:35|11:07]]
|- id="t11:07:59"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | do that for all the revisions i mailed and that should give you an aggregate patch that can then be retrofitted in the 4_4-plugin branch.
|| [[#t11:07:59|11:07]]
|- id="t11:08:39"
! style="background-color: #854685" | BoChao
| style="color: #854685" | so that script from that link, I run that in the gcc-4.4-plugin directory right?
|| [[#t11:08:39|11:08]]
|- id="t11:09:32"
! style="background-color: #407a40" | humph
| style="color: #407a40" | BoChao: all svn commands should be run inside the working directory (i.e., what you checked out with svn co)
|| [[#t11:09:32|11:09]]
|- id="t11:10:32"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: no, the script svn-get-rev needs to be run inside your copy of 'trunk' because those revision numbers are against trunk.
|| [[#t11:10:32|11:10]]
|- id="t11:10:47"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | if you run svn-get-rev with those numbers inside the 4_4-plugin tree, you'll get an empty output.
|| [[#t11:10:47|11:10]]
|- id="t11:10:56"
! style="background-color: #854685" | BoChao
| style="color: #854685" | ok
|| [[#t11:10:56|11:10]]
|- id="t11:12:35"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so, you'll have two gcc trees checked out. trunk and gcc-4_4-plugin.
|| [[#t11:12:35|11:12]]
|- id="t11:23:29"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph/ctyler/BoChao: i'm sending the announcement about the branch + rules for it. Are you all subscribed to gcc@gcc.gnu.org?
|| [[#t11:23:29|11:23]]
|- id="t11:24:03"
! style="background-color: #407a40" | humph
| style="color: #407a40" | I am not, no
|| [[#t11:24:03|11:24]]
|- id="t11:27:12"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | not really necessary, you can track it from the archives. the announcement won't say anything you don't already know.
|| [[#t11:27:12|11:27]]
|- id="t11:27:39"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | the one rule i'm imposing on the branch is that it will only accept backports from mainline. i don't want it to become a sandbox for new functionality.
|| [[#t11:27:39|11:27]]
|- id="t11:28:03"
! style="background-color: #407a40" | humph
| style="color: #407a40" | seems reasonable
|| [[#t11:28:03|11:28]]
|- id="t11:30:09"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: patches for this branch should be posted to gcc-patches@gcc.gnu.org and include the tag [44-plugins] in the Subject.
|| [[#t11:30:09|11:30]]
|- id="t11:33:50"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: i am not subscribed gcc@gcc.gnu.org
|| [[#t11:33:50|11:33]]
|- id="t11:34:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: this is an excellent time to subscribe. tune your filters, though.
|| [[#t11:34:16|11:34]]
|- id="t11:34:37"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | gcc@ is for discussions on development, gcc-patches@ is where we post all patches.
|| [[#t11:34:37|11:34]]
|- id="t11:35:06"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | we're cavemen and don't believe in tracking patches via modern ways.
|| [[#t11:35:06|11:35]]
|- id="t11:35:46"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: how do i subscribe?
|| [[#t11:35:46|11:35]]
|- id="t11:35:55"
! style="background-color: #407a40" | humph
| style="color: #407a40" | the thing about getting students involved, is that they have no habits to break, so whatever you do is what they become accustomed to doing
|| [[#t11:35:55|11:35]]
|- id="t11:36:16"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | BoChao: http://gcc.gnu.org/lists.html choose gcc-patches and gcc.
|| [[#t11:36:16|11:36]]
|- id="t11:36:20"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | humph: haha
|| [[#t11:36:20|11:36]]
|- id="t11:36:45"
! style="background-color: #854685" | BoChao
| style="color: #854685" | dnovillo: what is teh argumetn I need to type in for the script
|| [[#t11:36:45|11:36]]
|- id="t11:36:48"
! style="background-color: #854685" | BoChao
| style="color: #854685" | usage: svn-get-rev rev
|| [[#t11:36:48|11:36]]
|- id="t11:37:06"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | 'rev' is the number. those are the revision numbers i sent in my email.
|| [[#t11:37:06|11:37]]
|- id="t11:37:34"
! style="background-color: #854685" | BoChao
| style="color: #854685" | oh..ok, just type in those numbers in 1 by 1?
|| [[#t11:37:34|11:37]]
|- id="t11:37:58"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | yup. i would try to apply 1 patch at a time.
|| [[#t11:37:58|11:37]]
|- id="t11:38:22"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | in theory, the groups of revisions i sent should give you a buildable compiler every time.
|| [[#t11:38:22|11:38]]
|- id="t11:38:39"
! style="background-color: #42427e" | dnovillo
| style="color: #42427e" | so, apply the first group of revs. check that the compiler builds. then apply the second, etc.
|| [[#t11:38:39|11:38]]
|}
