On Fri, 2007-08-03 at 09:36 +0200, Holger Schurig wrote: > > I see. One thing I didn't like in quilt is that I have to > > decide what I'm going to do before actually changing the > > sources. > > All I have to decide beforehand is the name of patch. In stgit > this is the same. However, stg is worse, because there I even > have to enter a description of what I'm about to do beforehand. > *)
But unlike quilt, you don't have to do anything before editing the sources. You can create a patch after the changes are done. Or you can revert the changes. Having to do anything before editing reeks of version control systems predating CVS, where files had to be checked out for editing. My complaint about stgit is that I have to write the description without seeing the changes. I just noticed "stg new -s", but it's broken. Generally, stgit follows quilt too closely here. "stg new" and "stg refresh" should be merged, or one of them should be optional. > Sometimes, I just make patches in quilt, then I do "quilt > refresh", "quilt pop -a", "cd patches" and modify the patches > and series file manually, e.g. by moving one patch from one file > into the other. The "cd ..", "quilt push -a" and off I am. That > the "database" of quilt is in a known format and I can hack on > it with an editor is a plus for me :-) That's a very cool feature that stgit should learn. > That said: once I'm finished with quilt-things, I'm using stg > import to import this into git and use git to send it off to the > mailing list. I'm not working with stg on the first place, > because quilt is noticably faster than stg. Perhaps periodic repacking with git-gc could speed up things a bit. But the search for changed files is actually for your protection, and should be appreciated IMHO. > *) in stgit I can do "stg refresh -e" to edit the description > afterwards "stg refresh -es" and "stg export -np" are my favorite commands. I'm going to post all my ideas to the git list right now. -- Regards, Pavel Roskin _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
