One is expected to use `git llvm push`. For more information, please see: https://llvm.org/docs/GettingStarted.html#for-developers-to-commit-changes-from-git
> On Sep 3, 2019, at 7:06 PM, David Greene via cfe-dev <[email protected]> > wrote: > > What is the expected way to do commits? Do we push directly to master > after a rebase? I know there has been talk of using GitHub pull > requests and I would be in favor of that. What's the status of those > discussions? > > -David > > Tom Stellard via Openmp-dev <[email protected]> writes: > >> Hi, >> >> I've created a text file[1] in the SVN repository that developers can >> update in order to request commit access to the GitHub repository. >> All you need to do is add a line in the form of >> $SVN_USERNAME:$GITHUB_USERNAME >> >> Please add your information to this file before SVN becomes readonly >> on October 21 to avoid a gap in commit access. More details can be found in >> the phabriactor review[2] that updates the developer policy. >> >> We will be verifying that the svn committer matches the username in the >> file, so you can only request access for yourself and not someone else >> >> Thanks, >> Tom >> >> [1] >> https://llvm.org/viewvc/llvm-project/meta/trunk/github-usernames.txt?view=markup >> [2] https://reviews.llvm.org/D66840 >> _______________________________________________ >> Openmp-dev mailing list >> [email protected] >> https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev > _______________________________________________ > cfe-dev mailing list > [email protected] > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev _______________________________________________ lldb-dev mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
