What's the Git approach to publish a patch queue?

Question

I am used to Mercurial mq extension to maintain a set of custom patches over the upstream. They can be published as a separate repository aside from the upstream. Now in git

Answer 1

To summarize the answers and comments. With git there are two approaches to publish small custom modifications over the remote upstream:

• forget rebase, publish a branch and new merges as necessary
• declare that a branch is rebasing, just rebase and publish (pro: clean history, contra: can be a pain to be used continuously by someone else, example: linux-next)

So far the pure patch queue workflow doesn't seem to be doable with git, but guilt seems to be be very close to mq, even names of the commands. It doesn't allow for a version-controlled (and publishable) patch queue.