git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Anderson <zelnaga@gmail.com>
To: Tait <git.git@t41t.com>
Cc: git@vger.kernel.org
Subject: Re: a few beginner git questions
Date: Sat, 6 Mar 2010 23:02:20 -0600	[thread overview]
Message-ID: <15b345f1003062102l22ac2d2fn3ed5b73221bf4216@mail.gmail.com> (raw)
In-Reply-To: <20100306070533.GL2480@ece.pdx.edu>

On Sat, Mar 6, 2010 at 1:05 AM, Tait <git.git@t41t.com> wrote:
>> 4. I clone git://github.com/symfony/symfony.git to c:\git\test\root
>> and clone that to c:\git\test\clone.  I then blank
>> c:\git\test\clone\README, stage it, commit it and push it and the
>> change does not appear in c:\git\test\root\README.  I then reopen Git
>> Gui and open root and there I see the blanked README as an uncommited
>> state change.  I commit it and the change still does not appear in
>> c:\git\test\root\README.  Is this what Git should be doing?
>
> You shouldn't push into a non-bare repository (unless you know what you're
> doing and really mean it). This:
>        http://git.wiki.kernel.org/index.php/GitFaq#Why_won.27t_I_see_changes_in_the_remote_repo_after_.22git_push.22.3F
> explains a bit more on the subject.

How, then, do I update code?  ie. I perform my initial clone, make
some changes and commit / push them.  Someone else then comes along,
makes some changes and commits them.  The next day, I do Remote ->
Fetch from -> origin to update my code to the latest in Git but
c:\git\test\clone\README is exactly the same as it was before.  How do
I update the initial clone such that I can edit the updated files?

  parent reply	other threads:[~2010-03-07  5:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06  6:42 a few beginner git questions Thomas Anderson
2010-03-06  7:01 ` Allan Wind
2010-03-06  7:05 ` Tait
2010-03-07  2:23   ` Thomas Anderson
2010-03-07  9:08     ` Dmitry Potapov
2010-03-07  5:02   ` Thomas Anderson [this message]
2010-03-07  8:50     ` Dmitry Potapov
2010-03-08 18:55     ` Tait
2010-03-07  9:39 ` Junio C Hamano

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=15b345f1003062102l22ac2d2fn3ed5b73221bf4216@mail.gmail.com \
    --to=zelnaga@gmail.com \
    --cc=git.git@t41t.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;
as well as URLs for NNTP newsgroup(s).