Skip to content

Update #item_base.txt - #19

Open
Vex-- wants to merge 1 commit into
sanscriptum:englishfrom
Vex--:patch-6
Open

Vex-- wants to merge 1 commit into
sanscriptum:englishfrom
Vex--:patch-6

Conversation

@Vex--

@Vex-- Vex-- commented Dec 14, 2014

Copy link
Copy Markdown

Numerous grammar/readability edits. Fixed the description of the formal suit (the in-game description was a misplaced copy-paste of the medical gown). Not sure about "ringing monists" under exotic outfit description.

Numerous grammar/readability edits. Fixed the description of the formal suit (the in-game  description was a misplaced copy-paste of the medical gown). Not sure about "ringing monists" under exotic outfit description.
@sanscriptum

Copy link
Copy Markdown
Owner

Umm... As you can probably tell, this is not how you make commits. You've created a lot of patch branches with only one commit. I suggest using git programs with gui such as GitExtensions, so you can make commits in one branch. This is why you should not use website interface for committing. Also I can merge changes from your fork without pull requests. I'll do that when I'm done with update development.

@Vex--

Vex-- commented Dec 15, 2014

Copy link
Copy Markdown
Author

Thanks for letting me know. As you can probably tell, this is my first time using Github. Using one branch per one file was how I thought their introduction said to do it... I guess doing the work, then figuring out the environment isn't always tidy. I'm installing GItExtensions right now, but I also have a running qsp file with all my edits merged, if that helps. I should be able to figure out GitExensions by today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants