One of the real problem areas I haven't solved particularly well: For complex project I might have several cloned repos or branches, each forked off to solve a

One of the real problem areas I haven't solved particularly well: For complex project I might have several cloned repos or branches, each forked off to solve a particular issue, develop a specific feature, or try a particular approach. There doesn't seem to be a very good or integrated way to keep track of the purpose or intention of each branch/repo. It can be very confusion when trying to switch between them. "What was I doing in THIS repo? Where was I? Where was I heading?" I've tried keeping a file `THISBRANCH` in each with just a one or two line "what's going on here?" description. Better than nothing--but it's not well-integrated into other repo commands/actions, and is a pain when merging back toward a more upstream repo. In general, Mercurial and Git don't seem to do a very good job tracking "intent" metadata about each repo/branch.