In message <[EMAIL PROTECTED]> you wrote:
> If I find the time, I'll add some sort of pattern-match parameters to
> be tried against the commitmsg to extract likely head/branch names
> where we are merging from. My problem right now is that the only cvs
> repo with interesting branches and merges I have is huge, and takes an
> hour to import. That puts a damper on things, unfortunately.
In a first step, and to try things out, it might be sufficient if one
could feed in this information manually, like by providing a list of
PatchSet ID's which are known to be merges ?
At least in my case where the number of branches and merges is small
this would be completely satisfactory.
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
What is mind? No matter. What is matter? Never mind.
-- Thomas Hewitt Key, 1799-1875
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html