On 17/10/2007, Linus Torvalds <[EMAIL PROTECTED]> wrote: > On Wed, 17 Oct 2007, Jaroslav Kysela wrote: > > I'm using stg on top of git for merging and easy tree rebasing, but the > > version might be old (I'll try upgrade at first): > > Ahh. That may explain it. stg may well be using the low-level git internal > commands (which *do* allow you to create any kind of commits you want, > including bogus empty ones).
StGIT indeed creates empty commits (don't think there is anything wrong with that specific version). Even the most basic command, "stg new", creates an empty commit which is than filled with changes via "stg refresh". Pushing patches may result in empty commits if a patch was merged upstream. Failing import also leaves an empty commit if the patch doesn't apply cleanly (and there is a .stgit-failed.patch file left). The "stg series -e" shows the empty patches and "stg clean" removes them but I wouldn't do this automatically as empty patches are allowed in StGIT, though in general for a limited time. I'll try to add warning/error to commands like "mail" or "export" to make the user aware. -- Catalin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
