From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: John Bito <jwbito@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Egit: how to merge after fetch (or pull)
Date: Thu, 9 Apr 2009 05:39:47 +0200 [thread overview]
Message-ID: <200904090539.47489.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <3ae83b000904081456i37ad65ate133469fa9a8f23c@mail.gmail.com>
onsdag 08 april 2009 23:56:23 skrev John Bito <jwbito@gmail.com>:
> I'd like to pull a branch before I do more work on it. After fetch,
> git status says the branch is behind origin by N commits.
>
> Can you tell me if there is an operation I can do via egit to get the
> origin changes onto my branch? (Most of the documentation I found for
> Egit appears to be before the fetch command was implemented.)
>
> In the mean time, I've been using 'git pull'. Unfortunately, I found
> that it's important to shut down Eclipse while doing a git operation
> using Cygwin - a GC run when Egit had a file open caused a problem in
> the repository that subsequent pushes propagated to my GitHub
> repository. It would be nice to work entirely within Eclipse.
A very recent update to msysgit (not git core and hence not cygwin) might help there.
Windows locks files when reading and the Eclipse plugin reads things from the
repo when changes are detected to see if anything interesting is there. The fix
in msysgit retries certain operations a number of times if they fail with access denied,
which is what you get if the file is open for reading.
Built-in pull is not there just yet.
-- robin
prev parent reply other threads:[~2009-04-09 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 21:56 Egit: how to merge after fetch (or pull) John Bito
2009-04-09 3:39 ` Robin Rosenberg [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=200904090539.47489.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=jwbito@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).