git/list[1] front-page[2] threads[3] people[4] search[5] about
 

keeping track of what a branch is for

From
ERE R <pc88mxer@gmail.com>
Date
Mar 19, 2009, 17:36 UTC
Message-ID
<3a69fa7c0903191036u24bbf613had88dbebb24335c4@mail.gmail.com>
Ok - here's another one...

I've started to create a lot of branches (like one per feature I'm working on), but I'm starting to have trouble keeping track of what each branch is for. Also, I'd like to keep track of a todo list for each branch.

Is there a good way to keep track of these details with git? Using a repository file kinda works except when merging back into the master branch.

Next: Junio C Hamano
Message 1 of 2 in “keeping track of what a branch is for”
  1. E RMar 19, 2009
  2. Junio C HamanoMar 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.