From: Ferry Huberts <ferry.huberts@pelagic.nl>
To: git@vger.kernel.org
Cc: Ferry Huberts <ferry.huberts@pelagic.nl>
Subject: [EGIT] [PATCH v3 0/1] Make sure to setup a clone the same as git-clone does
Date: Mon, 23 Feb 2009 19:55:22 +0100 [thread overview]
Message-ID: <cover.1235415204.git.ferry.huberts@pelagic.nl> (raw)
Currently the plugin does not setup the default remote branch, something that
git-clone does do.
This patch fixes the issue and makes the plugin setup a cloned repository
exactly the same as git-clone.
Ferry Huberts (1):
Make sure to set up the default remote branch correctly
.../org/spearce/egit/core/op/CloneOperation.java | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
next reply other threads:[~2009-02-23 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 18:55 Ferry Huberts [this message]
2009-02-23 18:55 ` [EGIT] [PATCH v3 1/1] Make sure to set up the default remote branch correctly Ferry Huberts
2009-02-23 19:51 ` [EGIT] [PATCH v3 0/1] Make sure to setup a clone the same as git-clone does 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=cover.1235415204.git.ferry.huberts@pelagic.nl \
--to=ferry.huberts@pelagic.nl \
--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).