-
Notifications
You must be signed in to change notification settings - Fork 327
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
Digitrax Extended Series 6 by John McMasters v3.5 #29
Conversation
Alain, Did you want this to be included in the main JMRI codebase? Only, as you closed the pull request, it has not yet been incorporated. |
Still in the learning phase ... |
Re-opened. Not exactly sure. Do I have write access or not ? If yes, how do I accept this pull request into the JMRI master? |
There are two changes that would be helpful before we accept this: |
I should note: you can edit those files directly in your clone of your fork of master, and this pull request should see the changes once you push the changes to your fork. (Or you can edit them directly in your fork on the GitHub website.) |
<!- ID: xxx -> comments
Came back to as it was in the GitHub version. So I don't have write access, do I ? |
On Sep 26, 2015, at 7:25 AM, Alain LM notifications@github.com wrote:
It looks like we can get them to work using got attributes. https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes I need to look at that page more closely later to get the proper keyword expansions. Other than the ID keyword, the one we use most frequently is revision.... Paul |
Well looking at a few files, it seems that all of the comments have been wiped out when moving to Git. |
Note that per the documentation:
|
I think we should move the discussion of keyword expansion to a separate issue, as it's a large question. I've started a new issue for it: #30 Bob |
Digitrax Extended Series 6 by John McMasters v3.5
Update NamedBeanBundle_fr.properties
Subject is self-explanatory.
My first attempt with Git / NetBeans.