At Thu, 02 Dec 2010 20:36:56 -0500,
Dave Abrahams wrote:

> > > > Snapshot is/was broken?
> > > 
> > > * It doesn't save the index by default anymore.  That's an
> > > alarming change.
> > 
> > You'll have to elaborate, if I stage a change and then stash, that
> > change is in the stash and comes out of it when I pop. 
> 
> Not in our experience.  Again, we'll try again, but for us, the
> working tree state was saved but the index comes back empty when we
> apply the stash with `a'.

Saving the stash always takes the index (that's git's default
behaviour). We established that popping in git doesn't restore it.

> > > It's one thing to fix newly-introduced bugs, but it's something else
> > > to be trying to fight against the current.  I guess we just want to
> > > make sure we're not swimming upstream.
> > 
> > To be frank David, I only see one commit from you. 
> 
> To be frank, one is more than zero ;-).  Remember, I considered myself
> an extremely happy user until yesterday, so there wasn't much
> motivation to change anything.  Finding time to work on magit has just
> become a higher priority.
> 
> > I don't know how big your anonymous band of backers ("we") is but I
> > get /far/ more feature patches than I do bug patches. Nothing is
> > free and so if you really want to help and ensure you're pride
> > remains intact when demoing magit, why not make a start on the ert
> > tests?

Ugh, did I say "you're"?

> I think my first moves have to be aimed at addressing some usability
> issues,

Make sure you air them on the mailing list first. Your idea of a
usability issue is another persons idea of a feature.

> even if you don't accept the changes upstream right away.
> After that, ert tests are top-of-my-list.  I need to learn how to
> write regression tests for Emacs packages anyway.

Great.

Cheers,
Phil

Reply via email to