In addition, once you do obtain svn commit access (maybe you already have
it), the suggested route is to hook up the llvm git module and run "git
*llvm* push" as described here:
http://llvm.org/docs/GettingStarted.html#for-developers-to-commit-changes-from-git
On Mon, Apr 15, 2019 at 1:58 PM Tim Northover via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Ramakota,
>
> On Mon, 15 Apr 2019 at 12:41, Ramakota Reddy via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > I have commit some changes successfully and unable to push those
changes
> using ‘git push’. First time I am submitting my changes.
>
> LLVM's canonical repository is still (for now) the SVN one, and you
> need an account there to push. There are instructions to get an
> account here:
> https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access.
> Meanwhile if you've had a patch approved you can ask someone to commit
> it for you in the same thread.
>
> Hopefully soon we'll be moving to a unified repository at GitHub.
>
> Cheers.
>
> Tim.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190415/e75b03a2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4849 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190415/e75b03a2/attachment.bin>