By the way:
Levend Sayar wrote:
> Yesterday one of my colleague tried to commit her two weeks of work.
If you really mean she wanted to make the first commit in two weeks,
that is just wrong. Usually you should commit at least every few
hours, and changes should be small and self-contained. Even in the
case of starting a new project or self-contained module, you should
commit a lot so you can go back to an older state if required. You
can use rebase -i later to clean up the work-in-progress commits.
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html