Loan's Beautiful Thoughts

* Feeding children, and taking them out for fun is easy. But teaching children to know and to follow in righteousness is hard.
* Cho con ăn ngon thì dể, cho con đi chơi thật thú vị cũng dể. Nhưng dạy con biết và làm theo dúng phải thì khó.

And from Billy Graham:
* Pleasures are the things that appeal to our flesh and to our lust. But joy is something else. Joy runs deep.
* Vui thích là điều xuất phát trong xác thịt và tình dục. Nhưng vui mừng thì khác hẵn. Vui mừng thật sâu đậm.

You can find more inspiration from Loan's musings and some of her favorite quotes here in English, and here in Vietnamese.

In Him.

Gnome3 Terminal does not execute my .bash_profile

If you have ever had this issue where changes to your .bash_profile do not take effect the next time you launch the gnome-terminal.  Well, do not worry.  Just open the gnome-terminal and go to Edit -> Profile Preferences _> Title and Command (tab), and you will see this:

Make sure that the "Run commnad as a login shell" is checked.  Then close, and close the terminal, and relaunch gnome-terminal, and you should see that your .bash_profile has been executed.

Hope that helps.

SOLUTION: fatal: Couldn't find remote ref {Branch} Unexpected end of command stream

Symptoms:  You issue a command and get the error like this:

$ git pull --rebase upstream a_branch_that_we_KNOW_is_there
fatal: Couldn't find remote ref a_branch_that_we_KNOW_is_there
Unexpected end of command stream

Assumptions:
1) the name of your remote repository is "upstream"
2) the branch you are pulling from is called "a_branch_that_we_KNOW_is_there"

There may be many ways to get this kind of error, but I suspect that I am not the only one who will get caught by this time wasting variant.

Reason: The reason you are getting the error is because the branch DOES exist at the correct repository, but you have requested a pull or fetch from the wrong repository.  And that branch name does NOT exist in the repo that you have requested a pull or fetch from.

How is that possible?

Cause: You may have accidentally added a remote name that points to the wrong git repository.

You can check the repository that your remote points to this way:

$ git remote show upstream
* remote upstream
  Fetch URL: https://github.com/pkg/pkg-module.git
  Push  URL: https://github.com/pkg/pkg-module.git
  HEAD branch: master
  Remote branches:
    some_other_branch_that_we_do_not_expect  tracked
    master                                   tracked
  Local ref configured for 'git push':
    master pushes to master (local out of date)

Or maybe this way:

$ git config --list | grep upstream
remote.upstream.url=https://github.com/pkg/pkg-module.git
remote.upstream.fetch=+refs/heads/*:refs/remotes/upstream/*

Either way, check very carefully that the Fetch URL is correct.  If you are silly like we are and have several modules in the same package, you may not have noticed the rogue:

git remote add upstream https://github.com/pkg/pkg-module.git

instead of the correct git repository:

git remote add upstream https://github.com/pkg/pkg-modulo.git

Easy to miss something like this, if you ask me.

Solution: remove the name of the remote that points to the wrong repo, and re-add the name back so that it points to the correct git repository.  Assuming your remote alias name is "upstream", you can fix that like this:

$ git remote rm upstream
$ git remote add upstream https://github.com/pkg/pkg-modulo.git

Now Your pull command should work successfully. But just in case, here is yet another way to check to make sure:

$ git ls-remote | grep a_branch_that_we_KNOW_is_there
From https://github.com/pkg/pkg-modulo.git
934a29d142efda2f40efced8a2126c5499162e03 refs/heads/a_branch_that_we_KNOW_is_there

Hope that helps.