From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Paul Tarjan <ptarjan@gmail.com>, git@vger.kernel.org, yury239@gmail.com
Subject: Re: Git Confusion
Date: Fri, 29 May 2009 06:44:26 -0700 (PDT) [thread overview]
Message-ID: <m3d49sauru.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090529125853.GB11785@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> On Fri, May 29, 2009 at 12:43:35AM -0700, Paul Tarjan wrote:
>
> > I'm new to git and probably doing something very dumb, but I can't
> > seem to resolve this.
> >
> > I have a remote repository and a local one. I ssh to the remote
> > machine, goto the repository directory (not a bare repository), edit a
> > file and commit it. All if fine.
> >
> > I leave the remote host and go into the local git directory. Doing
> > "git pull origin master" says "Already up-to-date." but there is a
> > file I changed remotely, and I want to pull it locally!
> >
> > The local repo was made with "git clone http://example.com/.git". I
> > have no branching (both are on master).
>
> Your repository is accessed over http. You need to run "git
> update-server-info" to build the files for clients to see the actual
> updates.
>
> Usually such a repo is bare, and gets updates only by push. In that
> case, enabling the update hook to run update-server-info is sufficient.
> But in your case, you are actually working on the remote repo via commit
> and other means, so there is no convenient way to always
> update-server-info after a change.
Well, he can always add git-update-server-info to post-commit hook.
>
> Is there a particular reason you cloned over http instead of over ssh?
Or git protocol?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-05-29 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:43 Git Confusion Paul Tarjan
2009-05-29 12:58 ` Jeff King
2009-05-29 13:44 ` Jakub Narebski [this message]
2009-05-29 13:52 ` Jeff King
2009-05-29 20:24 ` Paul Tarjan
2009-05-29 20:28 ` Avery Pennarun
2009-05-29 20:38 ` Jeff King
2009-05-30 0:41 ` Sitaram Chamarty
2009-05-29 20:45 ` Jakub Narebski
2009-05-30 1:32 ` Sitaram Chamarty
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=m3d49sauru.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ptarjan@gmail.com \
--cc=yury239@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 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).