On Wed, 25 Sep 2013 22:19:35 -0400
Tom Roche tom_ro...@pobox.com wrote:
[...]
23rw4kf 23 Sep 2013 09:39 Foo?
98bjttr 24 Sep 2013 12:34 Rollback! Bar.
07657ab 25 Sep 2013 10:11 Arrggg! Baz.
1495fcc 25 Sep 2013 23:45 Self-serving explanation.
Fred wants to push 1495fcc to the
Hello,
first of all, Fred should stop using such commit messages :-)
Seriously speaking, I think that's where git rebase -i comes in. Before
pushing, rebase on the last public commit, and edit/squash the unnecessary
commits.
Cheers,
Gergely
On 26 Sep 2013 04:19, Tom Roche tom_ro...@pobox.com
On Sep 26, 2013 12:05 AM, Gergely Polonkai gerg...@polonkai.eu wrote:
Hello,
first of all, Fred should stop using such commit messages :-)
Seriously speaking, I think that's where git rebase -i comes in. Before
pushing, rebase on the last public commit, and edit/squash the unnecessary
https://groups.google.com/forum/#!topic/git-users/nzwVr5li3cM
Tom Roche
How to restrict the commit history or messages that get pushed to a remote
repository?
...
Gergely Polonkai
...
git rebase -i[.] Before pushing, rebase on the last public commit, and
edit/squash the unnecessary
[caution: contains ASCII table, best viewed in monospace]
How to restrict the commit history or messages that get pushed to a remote
repository? What I mean:
Suppose a group wants to have a remote public repository (e.g., on github), but
its developers do not want their commit behavior and
