-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added -trace to TestRig. fixed code gen issue for trace listener #2
Conversation
added -trace to TestRig. fixed code gen issue for trace listener
Well, you don't have to create a pull request for every your change. You already a project developer and have "push" permission. Pull requests are for contributors. |
yeah, just testing / using as you suggested. ;) how do i get a freakin dev branch in antlr/antlr4 btw?
|
Hi On Mon, Jan 30, 2012 at 5:10 PM, Terence Parr <
cd your_project // hack your project // commit your changes // Double-check your commit // create a new remote branch and set upstream for local one
|
hmm…well, i got one easily by checking out antlr/antlr4 quickly. Now i'm learning about remote vs upstream and my forked stuff. fetch vs pull. ugh.
|
Wow. got it all figured out ;) Well, I was quite confused because I was in the wrong directory in one moment, but I think I'm working things out. Did you see my mail about antlr3-main vs main from p4? I want to make sure we have the right directory before we move on and turnoff p4. |
[dotnet] target: fix travis.yaml once again
Make C# NuGet package name more visible and add link to the package
trying my first pull from parrt/antlr4 to antlr/antlr4. Should go from dev to dev.