On Tue, Jan 13, 2009 at 7:56 AM, TK Soh <[email protected]> wrote:
> On Mon, Jan 12, 2009 at 4:58 PM, Steve Borho <[email protected]> wrote:
> > On Mon, Jan 12, 2009 at 8:16 AM, TK Soh <[email protected]> wrote:
> >>
> >> On Mon, Jan 12, 2009 at 2:32 AM, Steve Borho <[email protected]> wrote:
> >> > Hi TK, I've heard you mention a couple of times you've done some
> >> > preliminary work on this feature. Is this available for pulling?
> >>
> >> The work need some updating due the changes tortoisehg has seen it I
> >> last worked on it. I will try update it in a couple of days and share
> >> it with the team.
> >
> > I look forward to seeing this. Let me know if you need a hand.
>
> Here's the patch queue:
>
> http://bitbucket.org/tksoh/tortoisehg-hgshelve/
>
> Please give it a try and we can discuss it later. Do keep in mind
> right now very much a prototype with the basic support for
> shelve/unshelve.
>
Finally figured out how to coax the patch queue out of bitbucket (using
download link)
Is that supposed to be done easier somehow?
Likes:
hunk selection is very nice, well done
Dislikes:
no way to unshelve a single file
should it unshelve a file after it has been committed? this would be more
record-like
Non-sequitors:
Does the MS column need to be visible when the working copy has one
parent?
Having 'unknowns' visible at startup should be a sticky option. You risk
forgetting
to add/commit new files without it. You may also miss copies/renames.
What do you think of Qct's policy of pre-selecting files that Mercurial
would normally
commit by default (AMR)?
--
Steve
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
