From: Tomas Carnecky <tom@dbservice.com>
To: Simon C <simonchu.web@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to push changes from clone back to master
Date: Sat, 09 Jan 2010 02:00:26 +0100 [thread overview]
Message-ID: <4B47D52A.1050608@dbservice.com> (raw)
In-Reply-To: <1262986087967-4275010.post@n2.nabble.com>
On 1/8/10 10:28 PM, Simon C wrote:
>
>
> 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
If you asked that question in the official IRC channel, the answer would
be 'faq non-bare', which would cause the bot to send you a link to this
entry in the Git FAQ:
http://git.or.cz/gitwiki/GitFaq#Whywon.27tIseechangesintheremoterepoafter.22gitpush.22.3F
tom
next prev parent reply other threads:[~2010-01-09 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 21:28 How to push changes from clone back to master Simon C
2010-01-09 1:00 ` Tomas Carnecky [this message]
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=4B47D52A.1050608@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=simonchu.web@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.