From: Andreas Ericsson <ae@op5.se>
To: Tim <opensourcetim@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: correct workflow with bare repo and pull?
Date: Tue, 30 Jun 2009 08:28:22 +0200 [thread overview]
Message-ID: <4A49B086.30000@op5.se> (raw)
In-Reply-To: <583913.73865.qm@web52205.mail.re2.yahoo.com>
Tim wrote:
> Myself and the other developer on the team have private repos, and we
> push to a bare repo (which we use for Hudson builds). For now we only
> use the master branch. No other remote repos. When another developer
> pushes changes to the bare repo, and I pull them, all of the files they
> pushed show up as modified on my box when I do "git status" (even
> though I had not modified them). How to avoid this?
Make sure neither of you modify the executable bit on the files, and make
sure your editors work the same in both ends wrt the last line and white-
space at the ends of lines.
Also make sure you have compatible crlf settings in your git configs.
If your editors are what's causing the problem, you should only see the
files you've actually opened in your editor as being different. If it's
your git configuration, "git pull && git status" should show differences
immediately. "git help config" and searching for core.autocrlf should
point you in the right direction to what might be causing the error.
If it's modechanges that's the problem. core.filemode may also be a
possible source of errors (it has to be "false" on windows but can be
"true" on systems with posix permissions).
> Also, one
> developer saw really strange results when they did a "git pull origin
> master" and "git status" -- the paths shown below do not exist in the
> local work area. These files have always lived under a-core/.... so it
> is really odd that they show up under a-web
> # On branch master
> # Changes to be committed:
> # (use "git reset HEAD <file>..." to unstage)
> #
> # new file: a-web/src/main/java/com/blah/account/Account.java
> # new file: a-web/src/main/java/com/blah/account/AccountType.java
> #
> # Changed but not updated:
> # (use "git add/rm <file>..." to update what will be committed)
> # (use "git checkout -- <file>..." to discard changes in working directory)
> #
> # deleted: a-web/src/main/java/com/blah/account/Account.java
> # deleted: a-web/src/main/java/com/blah/account/AccountType.java
>
> What are we doing wrong?
>
Hard to tell without knowing what the repository looks like. Is this
a repo you can share with us?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-06-30 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 0:01 correct workflow with bare repo and pull? Tim
2009-06-30 6:28 ` Andreas Ericsson [this message]
2009-06-30 8:14 ` Robin Rosenberg
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=4A49B086.30000@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=opensourcetim@yahoo.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).