From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: git@vger.kernel.org
Subject: Re: [EGIT RFC] Git Repository Exploring
Date: Tue, 5 Feb 2008 23:04:48 +0100 [thread overview]
Message-ID: <200802052304.48382.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <47A8841E.7050009@intelinet.com.br>
tisdagen den 5 februari 2008 skrev Roger C. Soares:
> My first contact with egit was with the version that comes with fedora.
> I tried to "checkout" a git project in many ways but none seemed to
> work. Only a week later I read somewhere on the web that I had to import
> an already cloned repo into eclipse and then go to Team -> Share Project.
>
> So, to make it easier for new users coming from cvs or svn, my current
> idea is to add a Git Repository Exploring Perspective and as soon as
> possible give an warning that clone isn't there yet and how the user
> should proceed. Would it be ok?
Yes, but what infrastructure would that exploring facility work on?
Known gitweb's?
Anyway, by that time my fetch might be there. I was thinking about integrating
it with File/Import and add a new Git>Clone source and just have a dialog where
one could paste a URL-ish, user/password, or ssh public key. If you want to have
go at the dialog, I'd appreciate that.
I need to do at least basic local ref management in the fetching first, and maybe
some more test cases. Speed is slightly slower than the C version, but not terribly
so.
-- robin
next prev parent reply other threads:[~2008-02-05 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 15:43 [EGIT RFC] Git Repository Exploring Roger C. Soares
2008-02-05 22:04 ` Robin Rosenberg [this message]
2008-02-07 0:35 ` Roger C. Soares
2008-02-05 22:10 ` 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=200802052304.48382.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=rogersoares@intelinet.com.br \
/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.