Paul wrote:
this reminds me of a question: how likely is it that a checkout of
any arbitrary git commit will work well?
Right now would be fine :-)
i'd like a sense of whether i'm likely to hit the middle of
development churn.
In general, if it's been quiet for a few days, I would expect
it's good. To get a snapshot of recent activity, see especially
the lower part of http://git.savannah.gnu.org/cgit/nmh.git
skimming the logs, there's what looks like a fair amount of "oops,
didn't mean that", or "back out test code" sort of stuff.
Mistakes happen, especially when hacking certain areas.
As far as the test code goes, that's an artifact. Lyndon's
buildbot picks up only changes to master so they've got to be
on it. This doesn't happen often and is very clustered, such as
when a new platform is added to it.
We could get more sophisticated, but at this point I don't
think it's worth the effort and resources. Though neither are
mine.
somewhat related: does everyone use git rebase before pushing?
when possible, i've found that rearranging/squashing my development
commits before pushing upstream (mainly using "git rebase
--interactive") can help reduce clutter and make for more concise
changesets. folks are probably doing this already, but thought i'd
mention it just in case -- the ability to rearrange patches on
private branches is one of git's finest features.
I don't, because I haven't digested the git rebase man page.
And I'm so wary of rebase (search "git rebase dangerous") that
I just stay away from it. If you would educate me on how to
do it safely, I'd consider it.
David
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers