On Wed, Mar 11, 2009 at 07:02:07PM +0900, Nanako Shiraishi wrote: > I'm sorry, but I don't understand why you want to keep the entries in > the reflog that were made before you pushed your branch to make it > public in this scenario. > > Especially because you are relinquishing the authority to the public > repository by wishing to be able to "track" it, you can't rewind the > branch beyond the point you initially pushed out any more. At that > point, wouldn't it make more sense to drop the old reflog data and > pretend as if the branch were fetched from the branch from your public > repository it now follows, just like everybody else does? That only means that you cannot rewind back to some spot in the reflog. There is nothing to say that you cannot pull useful ideas from the reflog that you thought were failed experiments, and apply them as new commits. -Peff -- 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
