Re: [PATCH 2/2] reflog: ignore expire-unreachable for "HEAD" reflog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 15 Apr 2010, Junio C Hamano wrote:

> Jeff King <peff@xxxxxxxx> writes:
> 
> > I think another way of addressing the same problem would be to redefine
> > "reachable" in this context as "reachable from any current ref".
> 
> I tend to agree, but I haven't thought through the case for entries that
> point at commits on detached HEAD.  My gut feeling is that unless they are
> connected to a real ref by now after all these expireunreachable days,
> they are "failed experiments" and deserve to get pruned, so "from any ref"
> would probably work well for them.

I'm a bit worried about this discussion.

What's the point of having a reflog for unreachable stuff if it is to be 
pruned faster than stuff that is already reachable without any reflog?


Nicolas
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]