Shelve extension does not work with crew
teekaysoh at gmail.com
Sun Nov 23 18:21:25 CST 2008
On Sun, Nov 23, 2008 at 10:35 AM, Bastian Doetsch
<bastian.doetsch at gmx.de> wrote:
> Hi there,
> I've tried the hg shelve extension and unfortunately it doesn't work anymore
> with crew. This is as far as I could understand due to some match-object
> changes in commitfunc.
Broken again? Dang! I'll take a look as soon as I find some time.
> Feature request:
> Moreover, I'd like to have a non-interactive option that would accept
> filenames for which to store diffs - basically like hg export. This way we
> could use the extension easier from MercurialEclipse. Currently, we have
> implemented our own native shelve, but this wouldn't be necessary if the
You mean you created your own version of shelve extension?
> non-interactive behaviour would be introduced. A call could look like this:
The interactive behavior is largely inherited from the Record
extension (at least in the early time when I started working on the
shelve extension), but I am sure we can do something about it.
> hg shelve -q --target <shelf-name> <file1> <file2> <file3>
> This would produce a diff-file with the name given with --target, much like
> hg diff behaves. The changes could then be unshelved by issuing:
> hg unshelve -q --source <shelf-name>
I feel it'd be simpler if we can use a common option name for --target
> which would do something like:
> hg import .hg/shelve-backup/<shelf-name>
Actually the diffs are save to .hg/shelve file. The .hg/shelve-backup/
directory is for storing the backup file during the shelve/unshelve
> So what do you think about this?
> Best regards
More information about the Mercurial-devel