On 10/4/07, Karl Hasselström <kha@xxxxxxxxxxx> wrote: > On 2007-10-04 01:29:17 -0400, Jon Smirl wrote: > > > for some reason the refresh from that command didn't close. Then stg > > pushed all the patches back after the edit and they got included > > into that patch. > > That's really weird. As far as I know there isn't a concept of > "closed" patches in StGit -- there's no need, because they're always > closed! Must be the other way around then, the next nine patches didn't get opened right. Their descriptions ended up in the right place but the deltas all ended up in the first patch. > > I did the 'stg refresh' from a directory that was not being tracked > > by git. It is in the .gitignore list. This appears to be the root of > > the problem. > > Mmmph. This is not the only StGit command that's apparently not safe > to run from a subdirectory. See e.g. https://gna.org/bugs/?9986. > > I plan to do some StGit hacking this weekend. I guess subdirectory > safeness ought to be at the top of my list ... > > -- > Karl Hasselström, kha@xxxxxxxxxxx > www.treskal.com/kalle > -- Jon Smirl jonsmirl@xxxxxxxxx - 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
