Re: [ANNOUNCE] Sharness v1.0.0

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

 



On Tue, Jun 14, 2016 at 02:43:19PM -0700, Junio C Hamano wrote:

> Jeff King <peff@xxxxxxxx> writes:
> 
> > I don't think the Git project would ever want to say "sharness is the
> > upstream, and we are now just a user of it". But I wonder if we could
> > break down test-lib.sh to keep the Git-specific parts separate, which
> > would make it easier for sharness to pull the other bits as a whole.
> 
> I took a quick look around, and it seems that this is an outdated
> fork made without getting much of the improvement from its upstream
> since it forked.  It does not seem to have lazy prerequisite, for
> example.

Yeah, I don't think it has kept up with our work. My statement above was
"I don't think we'd _ever_ want to consider sharness the upstream, even
if it were up to date", but obviously there would be a lot of work to
even get it there.

-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



[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]