llvm dev - Aug 2019 - 'git llvm push' other branches?

Hi folks,

I want to update the Release Notes for the release/9.x, but seems like 'git
llvm push' only supports commits to the master/trunk.
What's the current process for such patches?

Thanks,
Alex.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190812/36aed113/attachment.sig>

Ping?

On Mon 12. Aug 2019 at 09:56, Alex Denisov <1101.debian at gmail.com>
wrote:
> Hi folks,
>
> I want to update the Release Notes for the release/9.x, but seems like
> 'git llvm push' only supports commits to the master/trunk.
> What's the current process for such patches?
>
> Thanks,
> Alex.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190815/25a5f4fb/attachment.html>

On 08/15/2019 08:46 AM, Alex Denisov via llvm-dev wrote:
> Ping?
> 
In the release_80 branch, I updated[1] the script to commit to release_80
instead of trunk.  We could make a similar change in the release_90 branch.
That seems like the easiest way to get it to work.

-Tom


[1] https://reviews.llvm.org/rL356714
> On Mon 12. Aug 2019 at 09:56, Alex Denisov <1101.debian at gmail.com
<mailto:1101.debian at gmail.com>> wrote:
> 
>     Hi folks,
> 
>     I want to update the Release Notes for the release/9.x, but seems like
'git llvm push' only supports commits to the master/trunk.
>     What's the current process for such patches?
> 
>     Thanks,
>     Alex.
> 
> 
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

On Mon, Aug 12, 2019 at 9:56 AM Alex Denisov via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Hi folks,
>
> I want to update the Release Notes for the release/9.x, but seems like
'git llvm push' only supports commits to the master/trunk.
> What's the current process for such patches?
I just use SVN for release branches. For release notes it's
particularly easy since you only need to check out the docs/
directory:

$ svn co https://llvm.org/svn/llvm-project/llvm/branches/release_90/docs/
release_90_llvm_docs
$ cd release_90_llvm_docs
(edit ReleaseNotes.rst)
$ svn commit

If that doesn't work, I'm always happy to land patches for anyone on the
branch.

Thanks,
Hans