| 1 |
2009/7/23 Sérgio Almeida <mephx.x@×××××.com>: |
| 2 |
> I'm still not doing any commits as uselect can still break your python |
| 3 |
> environment while testing and i don't have the time to learn how to |
| 4 |
> handle branches in git. |
| 5 |
> |
| 6 |
|
| 7 |
It's probably wise to commit code in small-ish (and self-containing) |
| 8 |
discrete units each of which add something without breaking anything. |
| 9 |
Otherwise, it becomes very difficult to track down which change broke |
| 10 |
something via git bisect. I would recommend that you try to do this, |
| 11 |
if only just to learn how to make good commits. |
| 12 |
|
| 13 |
You could take a look at how the kernel folks handle this -- features |
| 14 |
go in as several small commits/patches. |
| 15 |
|
| 16 |
-- |
| 17 |
~Nirbheek Chauhan |
Archives