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

Re: Data Integrity & un-Commited Branches

From
BDBrian Scott Dobrovodsky <brian@pontech.com>
Date
Sep 15, 2007, 00:40 UTC
Message-ID
<2a8a071a0709141740l144b60aevdfec2b6cdab8bb60@mail.gmail.com>
In-Reply-To
<7vk5qtd3le.fsf@gitster.siamese.dyndns.org>

It was a misunderstanding of Git's work flow. By switching from 'an un-committed demo' to a previously committed master: I was expecting Git to give me the content last commited to master while at the same time preserving(without having to commit) the changes made in demo. Intuitively, this is how I expected Git to function.

Indeed, I read through the Crash Courses: 'Git for everyone' & 'Git for SVN users'.

-- 
Brian Scott Dobrovodsky
Next: Shawn O. Pearce
Message 1 of 12 in “Re: Data Integrity & un-Commited Branches”
  1. Brian Scott DobrovodskySep 15, 2007
  2. Shawn O. PearceSep 15, 2007
  3. Brian Scott DobrovodskySep 15, 2007
  4. Shawn O. PearceSep 15, 2007
  5. Junio C HamanoSep 15, 2007
  6. Brian Scott DobrovodskySep 15, 2007
  7. Jan HudecSep 15, 2007
  8. Shawn O. PearceSep 15, 2007
  9. Nikodemus SiivolaSep 15, 2007
  10. David KastrupSep 15, 2007
  11. Nikodemus SiivolaSep 15, 2007
  12. David KastrupSep 15, 2007

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.