git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Bastian Flinspach <bastian.flinspach@gerina.com>
Cc: git@vger.kernel.org
Subject: Re: Problems with EGit
Date: Wed, 3 Dec 2008 20:45:46 +0100	[thread overview]
Message-ID: <200812032045.47208.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <200812032021.57901.robin.rosenberg.lists@dewire.com>

onsdag 03 december 2008 20:21:57 skrev Robin Rosenberg:
> onsdag 03 december 2008 12:08:11 skrev Bastian Flinspach:
> 
> Hi Bastian,
> 
> > When i try to commit changes via the command line, everything works fine 
> > (well, except for me not being able to use my keyboard right for 
> > entering the commit message, but thats probably not important because i 
> > want to use EGit anyways).
> > Eclipse recognizes the repository and also displays changes i make. When 
> > trying to commit, however, i get a permission denied error.
> > 
> > So, this is basically where i am stuck. What can be the problem and what 
> > would be a solution? I assume, that i might have something to do with 
> > Linux users and privileges, but i am not yet versed enough to identify 
> > the problem on my own.
> 
> If Git does not have permission problems, neither should EGit, I think, In the
> workspace there is a file called .metadata/.log that you can inspect. See
> if you can find anything interesting, i.e. a seemingly relevant stack trace or
> other error message. The file can be quite large so try to cut it down.

Starting eclipse from a shell, may yield even more information.

-- robin

      reply	other threads:[~2008-12-03 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 11:08 Problems with EGit Bastian Flinspach
2008-12-03 19:21 ` Robin Rosenberg
2008-12-03 19:45   ` 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=200812032045.47208.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=bastian.flinspach@gerina.com \
    --cc=git@vger.kernel.org \
    /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).