Patching bad commits

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Michael Witten
Date: Monday, June 28, 2010 - 3:03 pm

Sometimes bisecting is less than useful because a number of commits
fail to build.

How about implementing something SIMILAR to "git notes" (perhaps
even using "git notes") to store and apply patches for such bad
commits?

For instance, bisecting could transparently apply any patches that
are necessary to make a bad commit actually buildable; such patches
could be distributed as usual for the benefit of others.

I'm thinking that a "patch note" could have 2 forms:

    * A plain patch file (or maybe a git tree of patches).

    * A reference to another commit that should be checked
      out instead.

Is this a worthwhile idea?

Sincerely,
Michael Witten
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Patching bad commits, Michael Witten, (Mon Jun 28, 3:03 pm)
Re: Patching bad commits, Avery Pennarun, (Mon Jun 28, 3:23 pm)
Re: Patching bad commits, Sverre Rabbelier, (Mon Jun 28, 3:24 pm)
Re: Patching bad commits, Antriksh Pany, (Mon Jul 5, 1:37 am)