git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wink Saville <wink@saville.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: [egit] How-to use egit
Date: Thu, 13 Dec 2007 16:11:30 -0800	[thread overview]
Message-ID: <4761CA32.80702@saville.com> (raw)
In-Reply-To: <200712140024.20667.robin.rosenberg.lists@dewire.com>

Robin Rosenberg wrote:
> torsdag 13 december 2007 skrev Wink Saville:
>   
>> Yes, I selected them all and a single jar was created which
>>     
> Never seen that behaviour. I'm surprised that would be the default.
> When I export I get separate jars.
>
>   
>> I then started eclipse and now I see: Window/Preferences/Team/Git
>> When I select "Git" in the above, I see "Hi, I'm an empty preference page."
>>     
> That's all there is for now, but it means the plugin is activated.
>
>   
>> But again, I don't see any new menu items that
>> would allow me to look at history or make commits.
>> Is there more I need to to install the plugin, or
>> maybe I just need a little guidance on how to use it.
>>     
>
> We do not actually implement any menus in the menu bar. The only menus
> are in the context (right click) menu on resources.
>
> Try right-click on a project in the project explorer and the Team menu>Share project.
>
> -- robin
>   
Got it:

One thing that would be helpful for me is the
relationship between the items in the context menu
and the git commands, it isn't obvious to me.

As a for instance, it seems "Update index (Refresh)"
is a "git add <file>" but what is "Assume unchanged"?

One other thing is there a "git diff" and or "git diff HEAD"?

Thanks,

Wink

      reply	other threads:[~2007-12-14  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 19:12 [egit] How-to use egit Wink Saville
2007-12-13  2:47 ` Jing Xue
2007-12-13 22:35   ` Wink Saville
2007-12-13 23:24     ` Robin Rosenberg
2007-12-14  0:11       ` Wink Saville [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=4761CA32.80702@saville.com \
    --to=wink@saville.com \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    /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).