[LLVMdev] git

[David A. Greene]

Jeffrey Yasskin <jyasskin at google.com> writes:

> This may be included in your second bullet, but we probably want a
> style guide of some sort for how to present changes when they're
> committed to the main repository. Should every commit pass tests, or
> is it ok to have 1 line per commit? 

I would say we'd want every commit to pass tests to aid bisecting.

> Should we create a merge commit with --no-ff to cap a series of
> changes and describe the feature? Do we want to try to keep the main
> repo's history mostly linear with local rebases or are lots of merges
> ok? Are there tools to help enforce whatever style people want?

The biggest question for me around stuff like this is how bisect works
with it.  I haven't used bisect at all so it would be helpful if someone
with some experience using it could comment.

                                -Dave