git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Jerome Yanga <jerome.yanga@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push from client is not updating files on server
Date: Tue, 06 Mar 2012 15:12:38 -0600	[thread overview]
Message-ID: <4F567DC6.4070903@gmail.com> (raw)
In-Reply-To: <CAC0z1F-bGikXZtLnd8d=3G+4okvNqZaxyrLjh4G3YzPpmqyxQA@mail.gmail.com>

On 3/6/2012 10:52 AM, Jerome Yanga wrote:
> My main objective is to create a central public Git server.  I had
> followed the instructions in the URL below to make it public.
>
> http://book.git-scm.com/4_setting_up_a_public_repository.html
>
> From the git client server, I can successfully clone projects in
> from the central public Git server using the command below.
>
> git clone
> http://<hostname_of_central_public_git_server>/<Project_name>.git
>
> My push seems to be successful too using the command below as I get
> the message "Everything up-to-date".
>
> git push
>
> However, when I log into the central public Git server and look at
> the files in the project, none of them have change.  I can only see
> the changes from the client via Gitweb.
>
Gitweb and gitk know how to look at .git (bare) repo and display the 
contents.  (I use gitk to verify that a push did what I wanted.)  There 
is no work-tree for a .git repo to do linux "ls" on.  If you really want 
to use commandline you would have to use git commands like git-show, 
git-ls-files, git-cat-file, git-log, etc., to display and interrogate 
the contents of git objects (tags, commits, trees, blobs) in a .git repo.

I suspect reviewing it in gitweb is sufficient to verify that the push 
did what you wanted.  (I don't use gitwet, yet.)

v/r,
neal

  parent reply	other threads:[~2012-03-06 21:12 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
     [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 [this message]
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=4F567DC6.4070903@gmail.com \
    --to=nkreitzinger@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jerome.yanga@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).