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

Tracking the untracked

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
May 6, 2009, 01:19 UTC
Message-ID
<93c3eada0905051819l92dc7ey331d69f009cc9c8b@mail.gmail.com>
Bug or feature? I don't know.

On the master branch I have some untracked files e.g., object modules, executables.

I create a branch B1 and add+commit the untracked files.

When I switch back to the master (git checkout master), the untracked files are no longer where I left them.

Basically, I'm trying to find a way of having a huge bunch of stuff in my repository and tracked, but which doesn't get pushed to the central program repository .. which has always just been source for us .. I figured I could stick it on a branch which doesn't get pushed. But that doesn't work for the reason mentioned.

One solution would be to have a class of files that is "unversioned but tracked".

Alternatively we could just bite the bullet and track everything.
Any ideas?

Cheers, Geoff Russell

Next: Johannes Schindelin
Message 1 of 7 in “Tracking the untracked”
  1. Geoff RussellMay 6, 2009
  2. Johannes SchindelinMay 6, 2009
  3. Thomas RastMay 6, 2009
  4. Geoff RussellMay 7, 2009
  5. Jakub NarebskiMay 7, 2009
  6. Thomas RastMay 7, 2009
  7. Geoff RussellMay 7, 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.