Catalin Marinas wrote: > On 19/11/2007, Jakub Narebski <jnareb@xxxxxxxxx> wrote: >> >> By the way, does StGIT write something meaningful by default in reflog >> messages? Because now my reflog looks like this: > > No, it leaves it up to GIT to write whatever it finds appropriate. But StGIT uses plumbing (or in the future perhaps PyGIT library). And plumbing does not write by itself reflog messages. It is left for porcelain (and StGIT being patch management interface is porcelain) to provide reflog message in GIT_REFLOG_ACTION. >> It would be really nice if StGIT wrote something meaningfull when >> updating ref, like "stg refresh: <something>", or "stg rebase: <sth>"... > > There is the 'stg log [<patch>]' command which shows the changes to a > specific patch. You can run it with -d (for the diff) or -g (to invoke > gitk). If I remember correctly StGIT is made to be more friendly to and with core-git. Providing reflog messages for "git reflog" / "git log -g" would be nice. Besides 'stg log [<patch>]' is a bit orthogonal: it describes history of a patch, and I want history of HEAD or of branch head (with things like refresh, new (!), goto, float / sink, rebase (!)). -- Jakub Narebski Poland - 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
