From: "Shawn O. Pearce" <spearce@spearce.org>
To: Francis Galiegue <fg@one2team.net>
Cc: git@vger.kernel.org
Subject: Re: Need help for migration from CVS to git in one go (ie, FORGETTING CVS history)
Date: Wed, 5 Nov 2008 15:23:48 -0800 [thread overview]
Message-ID: <20081105232348.GP15463@spearce.org> (raw)
In-Reply-To: <200811060014.57046.fg@one2team.net>
Francis Galiegue <fg@one2team.net> wrote:
> Finally, about the Eclipse plugin:
> * the README says that it has no push capacity, the popup menu says otherwise
> (last checked last Saturday)... What should I believe?
The README is out of date. Push is implemented, works, and folks
actually use it. That was a nice success from our GSoC program
this year.
> * if the plugin can push, can you configure from within the plugin what
> branches can be pushed where, or should you edit .git/config by hand?
I don't think you can edit saved configurations in the plugin UI.
The APIs are there underneath to do the reading/writing and most
of the UI to show a configuration is present, I just don't think
anyone has wired the two together for saved configurations inside
of .git/config. So yea, edit by hand.
> * "git stash": is it supported?
Not in Eclipse, no.
> * can you "copy" a commit, or even a set of commits, and "cherry-pick" them
> into another branch? Or even rebase a branch onto antoher?
Not in Eclipse, no.
--
Shawn.
next prev parent reply other threads:[~2008-11-05 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 23:14 Need help for migration from CVS to git in one go (ie, FORGETTING CVS history) Francis Galiegue
2008-11-05 23:23 ` Shawn O. Pearce [this message]
2008-11-05 23:34 ` Francis Galiegue
2008-11-05 23:44 ` Shawn O. Pearce
2008-11-06 1:28 ` Francis Galiegue
2008-11-06 21:18 ` Robin Rosenberg
2008-11-05 23:50 ` Petr Baudis
2008-11-06 1:15 ` Francis Galiegue
2008-11-06 3:08 ` Jakub Narebski
2008-11-06 12:13 ` Francis Galiegue
2008-11-07 0:34 ` Jakub Narebski
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=20081105232348.GP15463@spearce.org \
--to=spearce@spearce.org \
--cc=fg@one2team.net \
--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 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.