[Extension] Dirty hack of 'shelve' and 'unshelve' command
Erik Bågfors
zindar at gmail.com
Thu May 19 21:03:39 BST 2005
On 5/19/05, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Erik Bågfors wrote:
> | I think this is very useful. But I'd love to also see a "bzr commit
> | --interactive" or something like that, that would let the user select
> | the hunks he likes to commit.
>
> This idea really bothers me, and has since I heard about per-hunk commit
> in Darcs. Committing selected hunks that may make no sense out of
> context, with no opportunity for review, and only one chance to get it
> right? How is that better than typing one extra command?
What do you mean with "no opportunity for review" and "only one chance
to get it right"? You can always back out. Either by doing it the
darcs way and having a unrecord/uncommit command or simple reverting
what you did.
I'm not saying that the extra command is bad, it has lot's of uses..
> People clearly want this, even though from where I stand, it looks like
> they're on crack. So what am I missing?
Well, try it for a while and you realize something. Lot's of time you
do many small changes and they do make sense individualy. Basically,
I have been working on this thing for one hour, so I have lot's of
things to check in. Then a collegue comes in and says "can you change
this default value to 10 instead of 15". That's a one line change.
You can then do that change in the code you are in, and commit that
change. Then get on with what you are doing. The other way to do that,
would be to create a new checkout/branch, do the change there, get
back to what you were doing.
The next this is that going trough each hunk is acctually itself a
VERY good way to review what you did, What I noticed was that I often
did more than one thing. So I should really do more than one checkin.
Darcs makes that easy for me.
I'm not saying that this is a must, but I found it very useful in darcs.
/Erik
ps. Anyway, this is what's so great about plugins, even if you and
martin don't want it, someone else might want it and create a plugin.
More information about the bazaar
mailing list