From: Francis Galiegue <fg@one2team.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Need help for migration from CVS to git in one go (ie, FORGETTING CVS history)
Date: Thu, 6 Nov 2008 02:28:20 +0100 [thread overview]
Message-ID: <200811060228.21124.fg@one2team.net> (raw)
In-Reply-To: <20081105234425.GA2932@spearce.org>
[...]
> > > > * "git stash": is it supported?
> > >
> > > Not in Eclipse, no.
> >
> > What do you mean by this?
>
> I mean there's no implementation of git stash. Eclipse doesn't
> support git stash, the notion of the stash, the branch the stash
> is on. Its not in the Eclipse plugin.
>
While I'm a total newbie to Eclipse, and not that fluent with Java, this looks
surprising. Is it really Eclipse that is at fault here? Eclipse saves its
workspace (whatever it means to "save a workspace") when it exits, isn't
there an interface that you can implement that does "partial" saves, hence
git stashes?
> > > > * 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.
> >
> > Same question... What exactly is the problem with Eclipse wrt this kind
> > of operation?
>
> Its also not implemented in the eclipse UI.
Eclipse has the ability to apply patches AFAIK... Even though this may not be
equivalent to a git cherry-pick, wouldn't there be a way to extract at least
the diffs and commit messages and apply?
--
fge
next prev parent reply other threads:[~2008-11-06 1:31 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
2008-11-05 23:34 ` Francis Galiegue
2008-11-05 23:44 ` Shawn O. Pearce
2008-11-06 1:28 ` Francis Galiegue [this message]
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=200811060228.21124.fg@one2team.net \
--to=fg@one2team.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox