On Fri, Jun 13, 2008 at 09:16:42AM +0200, Andreas Ericsson wrote:
> To me, long-living stashes are useful because I can all of a sudden be
> pulled away from something I'm working on and set to work on something
> entirely different for up to 6 months (so far we haven't had a single
> emergency project run longer than that). It doesn't happen a lot, but
> it *does* happen.
So of course my first question is "then why didn't you use a branch?" :)
I'm not, by the way, trying to say "there is no good reason not to use a
branch." I am trying to figure out what the reasons are, because I
wonder if there is a more useful abstraction we can come up for handling
this situation.
Reading your (and others') responses, it seems like there are two
things:
1. Stashing is about saying "save everything about where I am now with
no hassle". IOW, it's one command, you don't have to decide what
goes and what stays, and you can pull it back out with one command.
And maybe there is a psychological component that you are not ready
to "commit" such a work-in-progress (I am extrapolating here, but I
know that when I first started with git, I was hesitant to commit
because of my experience with other systems).
2. Branches tend to get shared, and you don't want people to see your
stashes, because they are messy works in progress.
To deal with '2', I wonder if it would be worth making some branches
inaccessible to pushing/pulling (either via config, or through a special
naming convention).
For '1', I guess the only solution would be some way of making a topic
branch easy to stash and restore. And that would end up looking quite a
bit like stash; I would think the interface would be "git notstash
branchname". Which we sort of have with "git stash save <message>"
already. We could say "if you didn't provide a message, then it will be
gc'ed eventually, but if you did, then it lives forever". That would
work fine for my workflow (I don't bother naming stashes, since I
generally unstash them immediately). But it seems like an accident
waiting to happen for unsuspecting users.
> I think these are the options we're faced with:
> 1. Never expire stashes (don't shoot the user)
> 2. Don't treat stashes specially (shoot the user)
> 3. Don't purge stashes when auto-gc-ing (let the users shoot themselves)
> 4. Make the behaviour configurable (let the users shoot themselves)
> 5. Double the expiration time on stashes and warn for them when they should
> normally have expired (during gc, that is) (shoot the user, but warn first).
I am tempted by #3, which again matches my workflow. But again, it seems
like an accident waiting to happen for unsuspecting users.
So I think either #1 or #4 is reasonable. #4 probably isn't worth the
effort. If the stash reflog gets too cluttered, one can always expire or
clean it manually.
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
