fix small typo

[dedan]

No description provided.

[iggyvolz]

I believe it should be "time to spare", not just "time spare".

[dedan]

yes, you are right. I'll change that

[iggyvolz]

You might want to squash these commits to make them into one small "fix small typo" commit. Run git rebase -i 49b9e79, then change the first word of the second line to "squash" or "s". Now you may pick a message for your squashed commit.

After you do this, you will need run a git push --force to forcibly push the commits to your fork.

[dedan]

Hey Iggy,

thanks for that hint. I thought the rebases on already published branches
is frowned upon. I thought it will mess up the pull request. But now I read
about it and you are right. I'll do that later.

stephan

On Tue, Nov 18, 2014 at 9:10 PM, iggyvolz notifications@github.com wrote:

You might want to squash these commits to make them into one small "fix
small typo" commit. Run git rebase -i 49b9e79, then change the first word
of the second line to "squash" or "s". Now you may pick a message for your
squashed commit.

After you do this, you will need run a git push --force to forcibly push
the commits to your fork.

—
Reply to this email directly or view it on GitHub
https://github.com/maebert/jrnl/pull/310#issuecomment-63536346.

[iggyvolz]

@dedan: Yes, on a stable branch (such as the master branch maebert's jrnl), you should never rebase. But if you're doing a feature or bugfix branch, rebasing can help the master branch stay neat.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.