Git development
 help / color / mirror / Atom feed
From: "Brian Scott Dobrovodsky" <brian@pontech.com>
To: git@vger.kernel.org
Subject: Re: Data Integrity & un-Commited Branches
Date: Fri, 14 Sep 2007 17:40:56 -0700	[thread overview]
Message-ID: <2a8a071a0709141740l144b60aevdfec2b6cdab8bb60@mail.gmail.com> (raw)
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

       reply	other threads:[~2007-09-15  0:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2a8a071a0709140028o472bcr8c82bd88e37cc4e9@mail.gmail.com>
     [not found] ` <2a8a071a0709140036l5db62c0fl5af01f75f35610ba@mail.gmail.com>
     [not found]   ` <7vk5qtd3le.fsf@gitster.siamese.dyndns.org>
2007-09-15  0:40     ` Brian Scott Dobrovodsky [this message]
2007-09-15  2:51       ` Data Integrity & un-Commited Branches Shawn O. Pearce
2007-09-15  6:24         ` Brian Scott Dobrovodsky
2007-09-15  6:32           ` Shawn O. Pearce
2007-09-15  6:37           ` Junio C Hamano
2007-09-15  7:14             ` Brian Scott Dobrovodsky
2007-09-15  7:38         ` Jan Hudec
2007-09-15  7:51           ` Shawn O. Pearce
2007-09-15 13:11             ` Nikodemus Siivola
2007-09-15 13:59               ` David Kastrup
2007-09-15 17:14                 ` Nikodemus Siivola
2007-09-15 17:33                   ` David Kastrup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a8a071a0709141740l144b60aevdfec2b6cdab8bb60@mail.gmail.com \
    --to=brian@pontech.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox