Re: [boost] [Iterator] Fixing the default reference type of transform_iterator (#5127)

Subject: Re: [boost] [Iterator] Fixing the default reference type of transform_iterator (#5127)
From: Jeffrey Lee Hellrung, Jr. (jeffrey.hellrung_at_[hidden])
Date: 2012-04-21 21:34:22

On Fri, Apr 20, 2012 at 7:35 AM, Michel Morin <mimomorin_at_[hidden]> wrote:

> Jeffrey Lee Hellrung, Jr. wrote:
> >> Ticket #5127 describes this bug
> >>    https://svn.boost.org/trac/boost/ticket/5127
> >> and the ticket has a patch.
> >>
> >> Jeff, could you apply the patch, if it looks OK?
> >
> >
> > Sure, I'll try to get to it soon (presently doing an svn checkout on a
> new
> > laptop).
>
> Great!
>
>
> Here is how I set up my system (Mac OS X) for write access to
> the Boost subversion repository.
>
> 1. Modify the subversion configuration (~/.subversion/config)
> for mime-type and eol-style, according to the following link
>
> https://svn.boost.org/trac/boost/wiki/BoostSubversion#MIMETypesandEnd-Of-LineStyles
>
> 2. Creating a working copy with authentication
>  svn co  https://svn.boost.org/svn/boost/trunk boost-trunk --username
> YOUR_USERNAME
>
> Then, when I commit, I do the following command
>  svn commit --username YOUR_USERNAME -m "COMMIT_LOG"
>
>
> If the commit log contains
>  fix #XXXX (or fixes #XXXX, fixed #XXXX)
> then the trac ticket #XXXX is automatically closed by the post-commit hook.
> The commit log is also automatically added to the trac ticket as a comment.
>
> Some libraries close trac tickets when the fix is committed to trunk, but
> other libraries do not close trac tickets until the fix is merged to
> release.
> For such libraries,
>  refs #XXXX
> can be used to automatically add the commit log to the trac ticket
> as a comment (without closing the ticket).
>

Thanks Michael, this was very informative. I applied your patch and
committed (rev 78121). If I screwed something up in the process of
committing, apologies and someone please let me know!

A somewhat related but more general question: What is the procedure to get
changes from trunk into release? I understand we wait a couple days for the
tests to cycle, ensure there aren't any regressions, then merge to
release...and this last merging step in SVN I'm not familiar with. I
certainly don't want to mess anything up.

Thanks again and in advance,

- Jeff