From: Andreas Krey <a.krey@gmx.de>
To: Shawn Pearce <spearce@spearce.org>
Cc: git discussion list <git@vger.kernel.org>
Subject: egit vs. git behaviour (was: [RFC/WIP] Pluggable reference backends)
Date: Wed, 12 Mar 2014 11:26:01 +0100 [thread overview]
Message-ID: <20140312102601.GA26257@inner.h.apk.li> (raw)
In-Reply-To: <CAJo=hJt6zoJ=53JNUT6fLXM+5_4Af8enE67z3Ozv4DOz1jU1Eg@mail.gmail.com>
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?
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?
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
next prev parent reply other threads:[~2014-03-12 10:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 11:00 [RFC/WIP] Pluggable reference backends Michael Haggerty
2014-03-10 11:44 ` Johan Herland
2014-03-10 14:30 ` Shawn Pearce
2014-03-10 15:51 ` Max Horn
2014-03-10 15:52 ` Jeff King
2014-03-10 16:14 ` David Kastrup
2014-03-10 16:28 ` David Lang
2014-03-10 19:42 ` Jeff King
2014-03-10 19:56 ` David Kastrup
2014-03-10 17:46 ` Junio C Hamano
2014-03-10 17:56 ` Jeff King
2014-03-10 21:07 ` Michael Haggerty
2014-03-11 2:39 ` Shawn Pearce
2014-03-12 10:26 ` Andreas Krey [this message]
2014-03-12 16:48 ` egit vs. git behaviour (was: [RFC/WIP] Pluggable reference backends) Shawn Pearce
2014-03-11 10:56 ` [RFC/WIP] Pluggable reference backends Karsten Blees
2014-03-12 11:43 ` Michael Haggerty
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=20140312102601.GA26257@inner.h.apk.li \
--to=a.krey@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 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.