All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Tyler Silcox" <tsilcox@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: After successful push, all files are listed as modified, uncommitted changes on origin server
Date: Mon, 28 Apr 2008 08:40:29 -0700 (PDT)	[thread overview]
Message-ID: <m33ap6oump.fsf@localhost.localdomain> (raw)
In-Reply-To: <1d2b97db0804280834g8457151q658f54ff66e469@mail.gmail.com>

"Tyler Silcox" <tsilcox@gmail.com> writes:

> Myself and another developer are both experiencing this 'issue'. We
> will run a local commit and pull (on Macs), then push to the origin
> server (which is on Windows.) If you view the git status, it will list
> all files as modified, but I can't pull any details about what was
> modified with diff. In gitk, it shows all the files under 'local
> uncommitted changes, not checked in to index', but again, it doesn't
> tell me what was changed, it just lists the file names in the left
> column.
> 
> I'm thinking it's an OSX file browser process that is modifying the
> files' meta data when git is checking the repository. It is not
> affecting our workflow, but it is an annoyance. Any info that can help
> prevent this would be appreciated.

This is not the case of "do not push into non-bare repository"?
Or different autocrlf on both machines?

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      reply	other threads:[~2008-04-28 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 15:34 After successful push, all files are listed as modified, uncommitted changes on origin server Tyler Silcox
2008-04-28 15:40 ` Jakub Narebski [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=m33ap6oump.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tsilcox@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.