[PATCH libX11 3/4] man: Fix value of XkbAllComponentsMask in XkbGetKeyboard

Jeremy Huddleston jeremyhu at apple.com
Fri Feb 5 10:05:35 PST 2010

On Feb 5, 2010, at 01:57, Dirk Wallenstein wrote:

> I've done this for all of kbproto. Just a little procedural question.
> I have now patches that are related, but in different components. Should
> I put them into one thread of patches, optionally with a cover letter
> without component?

That seems to be historically the trend.  That's what I plan to do when I get around to the strict-aliasing issue.

> If I have a patch that requires a previous one that is not yet in the
> archives, do I just vaguely refer to that patch, or wait.

It doesn't seem like the changes you are referring to actually lend themselves to strict requirements... just man pages and stylistic cleanups.  I'm not sure how that can result in a requirement.

If you simply want to refer to commit <some hash>, then I'd say just leave that text out of the comment for now and insert the text after you actually push the first commit (so you have the correct hash to write in the second)


More information about the xorg-devel mailing list