git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon C <simonchu.web@gmail.com>
To: git@vger.kernel.org
Subject: How to push changes from clone back to master
Date: Fri, 8 Jan 2010 13:28:07 -0800 (PST)	[thread overview]
Message-ID: <1262986087967-4275010.post@n2.nabble.com> (raw)



I created master branch in git:

mkdir git_master;
cd git_master
git init
git add .
git commit

create a clone
git clone . ../git_clone1
create newfile
git add newfile
git commit .

then try to propagate changes to master
git push

it gave me some warning, and subsequent git push says everything is up to
date.
but I do not see the new file under git_master
-- 
View this message in context: http://n2.nabble.com/How-to-push-changes-from-clone-back-to-master-tp4275010p4275010.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2010-01-08 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 21:28 Simon C [this message]
2010-01-09  1:00 ` How to push changes from clone back to master Tomas Carnecky
2010-01-09  5:53   ` Simon Chu
2010-01-09  6:49     ` 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=1262986087967-4275010.post@n2.nabble.com \
    --to=simonchu.web@gmail.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).