Pete Grayson

I've taken another quick look at what's going on. The gist: When a new patch is created (`stg new`), there is metadata created in a variety of places: 1. `.git/patches`...

@akshedu yes, this issue remains open. And help is welcome, but... One of the core problems at play, as I mentioned in a previous comment, is that StGit still has...

Now that StGit has entirely eliminated the old/new metadata dichotomy, I have taken another look at this issue. There seem to be two separate asks here: 1) Allow slashes in...

Hi @smcameron. Sorry that you got hit by this bug--the corrupted stack state makes this one particularly nasty. Your approach for recovering was good. Newer versions of StGit (at least...

StGit is not going to allow patch names with slashes. Branch names with slashes are and will continue to be supported by StGit. As noted above, both StGit 1.x releases...

I took a quick look. The `-b/--branch` option to `stg mail` seems to be totally ignored. And it seems to have been ignored since `--branch` was introduced to `stg mail`...

I'm having a hard time reproducing this issue. I've tried some simple test cases that perform the `stg pop --spill`, `git reset`, `stg refresh`, `stg push` sequence with various intervening...

Yes, this helps. Thank you for providing this use case, @larsks. I agree that the error message provided by StGit is insufficient. There is a straightforward change to make StGit...

This use case and the problem of push-time conflicts with untracked files is not something I've run into before, or at least not enough to want StGit to do more....

I'm triaging old issues and trying to make sense of this one. Do we believe, @lkraav @chucklever, that there is a change needed for StGit? If there is a bug,...