[llvm-commits] ppc64 elf linux ReleaseNotes (for release_32 branch)

[Hal Finkel]

----- Original Message -----
> From: "Hal Finkel" <hfinkel at anl.gov>
> To: "Pawel Wodnicki" <pawel at 32bitmicro.com>
> Cc: llvm-commits at cs.uiuc.edu
> Sent: Monday, November 19, 2012 2:53:34 PM
> Subject: Re: [llvm-commits] ppc64 elf linux ReleaseNotes	(for	release_32	branch)
> 
> ----- Original Message -----
> > From: "Pawel Wodnicki" <pawel at 32bitmicro.com>
> > To: "Ulrich Weigand" <Ulrich.Weigand at de.ibm.com>
> > Cc: "Hal Finkel" <hfinkel at anl.gov>, llvm-commits at cs.uiuc.edu
> > Sent: Monday, November 19, 2012 9:44:15 AM
> > Subject: Re: [llvm-commits] ppc64 elf linux ReleaseNotes (for
> > 	release_32	branch)
> > 
> > 
> > > Hal Finkel <hfinkel at anl.gov> wrote on 16.11.2012 23:57:27
> > > 
> > >> The encoding fixes to get the integrated-as working were small
> > >> and
> > >> safe. I approve the following commits for merging into the
> > >> release:
> > >> r167861, r167862, r167863, r167875, r167860, r167864
> > >> (Ulrich, please let me know if that list is incomplete).

Merged into 3.2 in r168351.

> > >>
> > >> Also, this one is appropriate for merging:
> > >> r167737 - Make TOC contents deterministic

Merged into 3.2 in r168350.

Thanks again,
Hal

> > >>
> > >> Pawel, I'll be happy to handle the merging for you (once you
> > >> have
> > >> the ownership situation straightened out and re-open the release
> > >> branch).
> > 
> > 
> > For above set of commits (changeset) ownership is clear and it is
> > approved by the code owner. It can be merged in the 3.2 release
> > branch.
> > 
> > 
> > >>
> > >> Also, we should request that r167855 (a MachineCSE bug fix) be
> > >> merged into the release. I'm not the relevant owner, however.
> > > 
> > > This list looks complete to me.
> > > 
> > > Just to verify, since I'm not familiar with the details of the
> > > LLVM release process:  am I supposed to check any or all of
> > > those patches into the release branch?  Or is this all handled
> > > by the release maintainers?
> > 
> > 
> > This step is not crystal clear and left to the discretion of the
> > code owner/developer/release manager. I leave it up to you to
> > decide who will do it, just let me know.
> > 
> > In the end all I need is the list of commits (changeset) that has
> > been approved and merged into the 3.2 release branch.
> > 
> > So far we have these commits (changeset) below that have been
> > approved
> > r167861, r167862, r167863, r167875, r167860, r167864
> > r167737
> 
> I'll take care of the merging later today.
> 
> > 
> > 
> > You are also requesting r167855 to be merged -
> > in this case code owner has to be identified so it is on hold.
> > 
> 
> Evan has approved this merge (on list; Pawel, I also forwarded the
> e-mail to you to make your record-keeping easier). Unless it has
> already been done, I can merge this in with the others later.
> 
> Thanks again,
> Hal
> 
> > 
> > > 
> > > Bye,
> > > Ulrich
> > > 
> > 
> > Pawel
> > 
> 
> --
> Hal Finkel
> Postdoctoral Appointee
> Leadership Computing Facility
> Argonne National Laboratory
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
> 

-- 
Hal Finkel
Postdoctoral Appointee
Leadership Computing Facility
Argonne National Laboratory