search for: r168352

...nk version be merged in? The exact procedure is not spelled out but I think the easiest would be to merge relevant "ReleaseNotes.html" changes from the trunk, either let me know what to merge or just do it yourself. This approach has worked nicely for PPC target by merging r168189 and r168352 from the trunk into 3.2 release branch r168353. http://llvm.org/viewvc/llvm-project?view=rev&revision=168353 In any case at this point the above applies only to documentation changes. Pawel > > > On Mon, Dec 3, 2012 at 4:12 PM, 32bitmicro <root at 32bitmicro.com> wrote: &g...

...; The exact procedure is not spelled out but I think the easiest > would be to merge relevant "ReleaseNotes.html" changes from the trunk, > either let me know what to merge or just do it yourself. > > This approach has worked nicely for PPC target by merging r168189 and > r168352 from the trunk into 3.2 release branch r168353. > > http://llvm.org/viewvc/llvm-project?view=rev&revision=168353 > > In any case at this point the above applies only to > documentation changes. > > Pawel > > > > > > > > On Mon, Dec 3, 2012 at 4:12 PM...

What is the procedure for updating the release notes? I've been committing changes to the trunk version, should I be editing them elsewhere? Or will the trunk version be merged in? On Mon, Dec 3, 2012 at 4:12 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hi, > > > Are we going to have a mingw release this time? > > As far as I know there is no change from 3.1

Hi, > Are we going to have a mingw release this time? As far as I know there is no change from 3.1 and Mignw is considered experimental. Incidentally RC2 mingw32 binaries have been uploaded and are available for download and testing. http://llvm.org/pre-releases/3.2/rc2/clang+llvm-3.2rc2-i386-mingw32-EXPERIMENTAL.tar.gz Pawel > > > On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro