Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

The patch dance - OpenStack style.

Originally published .

If you are working on patches for OpenStack and you find yourself building patches that rely on other patches… what do you do? Well, you could maintain all your patches in one big directory and hope not to screw something up or “cross the files” but that would be down right lazy.

Seriously… lazy in the bad way… not at all lazy in the good way.

The right way to do things is a git branch per bug (or blueprint related patch) and then to rebase each “down-stream” bug from your appropriate “up-stream” bugs. That means you need to create a kind of “bug dependency” chart maintaining a tree like relationship between the various bugs.

As a prerequisite, I’ll assume you followed:

  • http://docs.openstack.org/developer/nova/devref/development.environment.html
  • https://wiki.openstack.org/wiki/GerritWorkflow

If you were a dummy and you managed to submit your first review on *master *(oh you fool!) then how do you fix this? Assuming your patch is safely up in gerritfor review already…

  1. roll back your master to head
  2. create a new local branch for your bug number
  3. use the “patch” link for your patch in gerrit
  4. after applying the patch, commit again and paste your old message in as the new commit message

The trick that makes this work is the special Change-Id:xxxxxxxx line at the end of the original message. This will tell gerrit to take your incoming patch as a new version of the old change.

What happens if you need to rebase your patch?

  1. git check out the master
  2. git fetch –all
  3. check out your bug branch
  4. git rebase master What happens if you need to have bug B based on bug A?

  5. git checkout master
  6. git fetch –all
  7. git branch bug/A
  8. git checkout bug/A
  9. do work for bug/A and possibly submit it to git review
  10. git checkout bug/A
  11. git branch bug/B
  12. git checkout bug/B
  13. do work for bug/B and possibly submit separately Need to make sure the master hasn’t drifted under bug A and B?

  14. git checkout master
  15. git fetch –all
  16. git checkout bug/A
  17. git rebase master
  18. … conflicts better result in your changing only code touched in bug/A or see the trick for how to “move” a patch to a branch above …
  19. git checkout bug/B
  20. git rebase bug/A The key is to keep the dependencies clean, feeding the master, then sliding up the branch dependency tree one bug at a time pulling forward the rebase from the last branch. Keeping each branch and patch separate should make other aspects of your life easier.

Explore the map · Browse by topic and date