Fix for issue #5800

[sathyamoorthi]

@JeffryBooher Fix for issue #5800 introduced by #4590

[ingorichter]

@sathyamoorthi Would you mind resolving the merge issue? I'd like to get this PR into master. Thank you.

[sathyamoorthi]

@ingorichter Shall i include other changes that this #5497 contains. They merged new file system into brackets. So we don't have issues to add other improvements that i gave in this PR (#5497)

[sathyamoorthi]

@ingorichter I think, i should have fixed your merge issues. Please take a look.

[ingorichter]

@sathyamoorthi wow, I think this looks like a lot of changes. I would recommend to check out a clean copy of the repo and apply your changes there and submit a new PR. I don't know how to fix the current PR to only contain the changes that you've made. Sorry for telling you that.

[njx]

This PR looks clean to me--only 3 line diffs and 4 commits (of which two were merge commits). Maybe GitHub got briefly confused?

[sathyamoorthi]

Ok let me give new PR. But, shall i include my other changes in this PR (close other improvements) to my new PR?

[sathyamoorthi]

@ingorichter I created two new pull requests.

#5951 - only few lines of changes to fix issue 5800.

#5952 - it has fix for issue 5800 along with some improvements. They were discussed already in this PR #5497.

But please pull any one of this before sprint 34. If you pull 5951, let 5952 open and assign it to @JeffryBooher. And i really don't know why my 'upstream/master' merge commits are stick along with these pull requests.

I only ran these two commands based on this document.

git fetch upstream
git fetch upstream/master

If you still feel anything weird, please do let me know. I can delete my entire fork and create new fork for this PR.

[ingorichter]

@njx weird. The page to show all the diffs was hardly rendered.