search for: arcpatch

...t will have no more use) Now, if the master to patchbranch diff has been properly submitted to Phabricator, all the steps above except the last one can be replaced by executing this: git checkout master arc patch D<revision> According to the docs, "this will create a new branch called arcpatch-D<Revision> based on the current master and will create a commit corresponding to D<Revision> with a commit message derived from information in the Phabricator review" This also sets the current branch to arcpatch-D<Revision>, so the only remaining thing to do is pushing the...

I was actually using `git llvm` in my daily workflow. Could you explain why we want people to move away from that script? In addition to the convenience, it prevented me from accidentally creating a new branch (which I did before with push once). Cheers,   Johannes On 5/11/20 11:43 AM, Zola Bridges via llvm-dev wrote: > Deleted this morning. Thanks! > Zola Bridges > > > On

Hello, Is there a way for Phabricator to retain the patches as originally uploaded? When using the "Download Raw Diff" button, it seems Phabricator reformats the patch, loosing the parent commit along the way, so often patches don't apply. The following works, because I've got the latest checkout on master, and the patch was rebased recently: F:\llvm-project>curl

Hi Vishal, Ruijie, Thanks for your interest in the project. To get started, the first task would be to merge the 5 patches on top of trunk llvm. The list of patches are listed in the project description: http://llvm.org/OpenProjects.html#llvm_mergesim Please create an account in llvm phabricator (reviews.llvm.org) if you haven't already, and put your patches there. Let me know if you have