On Sat, Dec 3, 2016 at 6:11 PM, Christian Couder <christian.cou...@gmail.com> wrote: > On Sat, Dec 3, 2016 at 6:04 AM, Julian de Bhal <julian.deb...@gmail.com> > wrote: >> but I'd be nearly as happy if a >> commit was added to the reflog when the reset happens (I can probably make >> that happen with some configuration now that I've been bitten). > > Not sure if this has been proposed. Perhaps it would be simpler to > just output the sha1, and maybe the filenames too, of the blobs, that > are no more referenced from the trees, somewhere (in a bloblog?).
Yeah, after doing a bit more reading around the issue, this seems like a smaller part of destroying local changes with a hard reset, and I'm one of the lucky ones where it is recoverable. Has anyone discussed having `git reset --hard` create objects for the current state of anything it's about to destroy, specifically so they end up in the --lost-found? I think this is what you're suggesting, only without checking for references, so that tree & blob objects exist that make any hard reset reversible. Cheers Jules P.s. Thank you for such a warm welcome while I blunder through unfamiliar protocols.
