Re: egit vs. git behaviour (was: [RFC/WIP] Pluggable reference backends)

From: Shawn Pearce <spearce@spearce.org>
Date: Mar 12, 2014, 16:48 UTC
Message-ID: <CAJo=hJvab468-PRMQJZ690A-ek8p01cwUOCkuy9KOQTRtt0FWQ@mail.gmail.com>
In-Reply-To: <20140312102601.GA26257@inner.h.apk.li>

On Wed, Mar 12, 2014 at 3:26 AM, Andreas Krey <a.krey@gmx.de> wrote:

Show 7 quoted lines

> On Mon, 10 Mar 2014 19:39:00 +0000, Shawn Pearce wrote:
>> Yes, this was my real concern. Eclipse users using EGit expect EGit to
>> be compatible with git-core at the filesystem level so they can do
>> something in EGit then switch to a shell and bang out a command, or
>> run a script provided by their project or co-worker.
>
> A question: Where to ask/report problems with that?

EGit developers have a bug tracker, from:

  http://eclipse.org/egit/support/

We see File a bug with a link to:

  https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EGit&rep_platform=All&op_sys=All

> We're currently running into problems that egit doesn't push to where
> git would when the local and remote branches aren't the same name. It
> seems that egit ignores the branch.*.merge settings. Or push.default?

I think this is just missing code in EGit. Its probable they already know about it, or many of them don't use these features in .git/config and thus don't realize they are missing.