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

Re: Tracking the untracked

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
May 7, 2009, 10:54 UTC
Message-ID
<93c3eada0905070354v2b8ff258m8db7b1d4968eb2ce@mail.gmail.com>
In-Reply-To
<200905071117.00162.trast@student.ethz.ch>
On 5/7/09, Thomas Rast <trast@student.ethz.ch> wrote:
Show 9 quoted lines
> Geoff Russell wrote:
> [...]
>  - Consider what happens if you were to recompile at this point, so
>   that you again have the _untracked_ (w.r.t. the 'master' branch)
>   build products, and then check out B1 again.  Git faces the choice
>   of either overwriting your worktree files (and losing them) or not
>   overwriting (and not doing the checkout right), so it will abort.
>   This is a corollary of what Jakub pointed out, Git will not lose
>   information unless told to.
Understood. Upon reflection, I can't think of a better alternative.
Cheers and thanks for the help,
Geoff.
Previous: Thomas Rast
Message 7 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.