On 10/12/06, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
BTW. currently I use StGIT to manage a series of commits on feature branch which implements step-by-step single feature, and would be later send as a patch series. With StGIT I can work on final patch in series, notice that underlying feature developed in earlier patch (earlier commit) needs modification, so I do refresh, pop until given patch, change patch, push all, and work on patch.
Or, if you made a modification but you want it committed to an underlying patch, use "refresh --patch" or "pop --keep; refresh". BTW, if it's not clear for me how to initially structure a patch series, I add everything to a patch and create underlying patches afterwards and pick hunks from the big one (usually manually, though native support in StGIT for this would be good, as someone pointed out on this list). If all the hunks in the big patch were added to other patches, pushing the big one should result in an empty patch automatically (because of the three-way merging) and can be safely removed. -- Catalin - 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