On 10/12/06, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
Catalin Marinas wrote: > Yes, only for updating HEAD. The refs in refs/patches/<branch>/ are > written directly. I initialy wanted to add patch history support using > reflogs and added "git-update-ref -m ..." for the patch commits but I > found slow the pushing operation a bit. Do you only want to track the > reflogs for HEAD? Yes, I want for StGit to provide reasons when updating HEAD. I know that StGit manages it's own versioning of patches not using reflog -- fine. What matters for me is reflog for HEAD after "stg commit; stg clean".
Just curious, do you run the "stg commit; stg clean" commands together and in this order? Neither of them would update the HEAD. The "commit" command simply removes the StGIT metadata for the applied patches since it no longer needs to track them (permanently stored to the repository). It doesn't change HEAD. The "clean" command only affects the HEAD if there are empty applied patches but after a "commit" there won't be any patches (only the unapplied ones which do not affect HEAD). Maybe we could have reflog info for "push", "refresh", some undo operations. Are they of any use (I haven't used them so I can't tell)? -- 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