[llvm] r181328 - Mention SystemZ in the release notes

Sean Silva silvas at purdue.edu
Tue May 7 10:20:23 PDT 2013


On Tue, May 7, 2013 at 11:14 AM, Rafael EspĂ­ndola <
rafael.espindola at gmail.com> wrote:

> > Yeah, that's tricky. In our git setup, is there a way to commit these
> > updates directly to the release branch? (I'm guessing that it's possible
> > from SVN, but I'm clueless about SVN). If it's not possible to commit
> > directly to the 3.3 release notes from git, then that would be a severe
> > inconvenience for git users.
> >
> > If it is possible to commit directly in some easy way, then we should
> > probably clean out the trunk release notes and have them be the "3.4"
> > release notes, with a prominent warning at the top to tell developers to
> > commit directly to the release branch for 3.3 updates.
>
> There are not that many patches that need to go to the branch, so in
> the past I have just used svn directly. I is fairly simple for this:
>
> $ svn co https://llvm.org/svn/llvm-project/llvm/branches/release_33
> $ build a patch with git, in the same way you would for sending it for
> review (the branch is missing on the git mirror, but I expect it to
> show up soon).
> $ cd /the/path/release_33
> $ patch -p1 < your_patch.patch
> $ svn commit
>
>
Ah, ok. Unfortunately, even though that's not so complicated, it does seem
to take at least an order of magnitude more time than simply committing "as
usual"; hence it would discourage people from adding to the release notes.

-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130507/eb659d74/attachment.html>


More information about the llvm-commits mailing list