This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 93641f30b7b2b330b28feb8d0bd49d736af3d7e9
tree 2809161ea3b98055165ff5f04b2e039ea01f1cc0
parent 420c4b3d8878156d04f45e47050ddc62ae00c68c parent 89237fe07e9c6d35687b3a473f09f4608a3625d8
tree 2809161ea3b98055165ff5f04b2e039ea01f1cc0
parent 420c4b3d8878156d04f45e47050ddc62ae00c68c parent 89237fe07e9c6d35687b3a473f09f4608a3625d8





Comments
I think we need better a bit more expressive commit messages than these “Merge branch ‘master’ of git://github.com/...”. Isn’t that possible when pushing ?
The real commit is here – http://github.com/josh/rails/commit/89237fe07e9c6d35687b3a473f09f4608a3625d8
And yes we are still working out a commit workflow to get the core commits name and author of the patch to show up in the commit log. If you have any good insight please message me.
I think it’s fine, unless we can somehow get this commit message to link to the relevant commits that were merged in.
Tip: “git merge” takes a ‘-m’ option just like commit, so you can provide a more verbose commit message if needed.
Rick, parent links to the previous commit and the merged commit.