From: Ramkumar Ramachandra <artagnon@gmail.com>
To: "Nico Schümann" <nico.schuemann@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Git-Automerge
Date: Sun, 4 Apr 2010 22:30:15 +0530 [thread overview]
Message-ID: <z2sf3271551004041000yaba616fbu20701cd505c5dbf7@mail.gmail.com> (raw)
In-Reply-To: <w2j1f05046e1004040947k3b812063ndbc2f8da3496effb@mail.gmail.com>
Hi,
On Sun, Apr 4, 2010 at 10:17 PM, Nico Schümann
<nico.schuemann@googlemail.com> wrote:
> $ git push
>
> But the changes do not appear on the master server. I have to type
>
> # git reset --hard or
> # git checkout -f
git-push only propagates history and updates refs. It doesn't touch
files in the working tree. I suspect you're pushing to a non-bare
remote. Please see --bare option in git-init (1) and this FAQ [0] on
the Git Wiki for more.
[0] https://git.wiki.kernel.org/index.php/GitFaq#Why_won.27t_I_see_changes_in_the_remote_repo_after_.22git_push.22.3F
-- Ram
prev parent reply other threads:[~2010-04-04 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 16:47 Git-Automerge Nico Schümann
2010-04-04 16:53 ` Git-Automerge Matthieu Moy
2010-04-04 17:00 ` Ramkumar Ramachandra [this message]
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=z2sf3271551004041000yaba616fbu20701cd505c5dbf7@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico.schuemann@googlemail.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 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).