From: Junio C Hamano <gitster@pobox.com>
To: Jerome Yanga <jerome.yanga@gmail.com>
Cc: git@vger.kernel.org, Ben Tebulin <nntp.20.jexpert@spamgourmet.com>
Subject: Re: git push from client is not updating files on server
Date: Tue, 06 Mar 2012 11:35:16 -0800 [thread overview]
Message-ID: <7vsjhlsetn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <jj5ih2$f0m$1@dough.gmane.org> (Ben Tebulin's message of "Tue, 06 Mar 2012 18:46:26 +0100")
[jc: resurrected JY as recipient]
Ben Tebulin <nntp.20.jexpert@spamgourmet.com> writes:
> You can only push to "bare-only repositories". These do not contain a
> working tree but only a .git directory.
That's a bit too strong. You do not have to limit your "push" into
"bare repositories" (drop "-only", there is no such word), but it is
perfectly fine to use "push" as a way to emulate a "fetch" that you
would wish you could but you cannot in the opposite direction.
What "push" does not do is to touch the working tree, and this is
intuitively understandable once you realize that "push" is an
opposite of "fetch".
> My push seems to be successful too using the command below as I get
> the message "Everything up-to-date".
>
> git push
It is somewhat strange that this _succeeded_.
When pushing into a repository with a working tree (i.e. "a non-bare
repository") and especially when trying to update its current branch
with such a push, "git push" would by default be refused, unless you
tweak a configuration variable or two on the receiving end. That is
an expert feature and I do not think that is being in use in this
particular scenario, so perhaps the push did _not_ succeed to update
the branch Jerome thought it updated, but instead updated a branch
that is _not_ the one that is checked out in the repository on the
receiving end of this push.
next prev parent reply other threads:[~2012-03-06 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 16:52 git push from client is not updating files on server Jerome Yanga
2012-03-06 17:46 ` Ben Tebulin
2012-03-06 19:35 ` Junio C Hamano [this message]
[not found] ` <CAC0z1F-Eg2DOLvd3aA5XCoEJjj1jC=VWVkTA+uc24=18h3pN7g@mail.gmail.com>
2012-03-06 20:37 ` Junio C Hamano
2012-03-06 21:12 ` Neal Kreitzinger
2012-03-06 21:21 ` Neal Kreitzinger
[not found] ` <CAC0z1F_eyMo4D8E2j15dOFhp-6tZ_ixacB6XcKfNpJategcsXQ@mail.gmail.com>
[not found] ` <CAC0z1F_LYRkReO1qqcjkWy6Vb3E0_oNo-0kSf15nGfQFAtXpdg@mail.gmail.com>
2012-03-06 23:07 ` Jerome Yanga
2012-03-06 23:32 ` Neal Kreitzinger
2012-03-07 0:28 ` Jerome Yanga
2012-03-07 1:11 ` Neal Kreitzinger
2012-03-07 2:23 ` Junio C Hamano
2012-03-07 2:34 ` Neal Kreitzinger
2012-03-07 11:04 ` Holger Hellmuth
2012-03-07 15:43 ` Jerome Yanga
2012-03-30 18:23 ` Jerome Yanga
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=7vsjhlsetn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jerome.yanga@gmail.com \
--cc=nntp.20.jexpert@spamgourmet.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).