Matthieu Moy writes:
> OTOH, having it leave in a subdirectory (e.g. $git/t/Sharness/), and
> synchronize with stg like subtree merge would be nice for the user. We
> already have something similar for gitk and git-gui, except that the
> synchronization is normally one way (subprojects merged int
Mathias Lafeldt writes:
> On Tue, Jul 17, 2012 at 8:31 PM, Ævar Arnfjörð Bjarmason
> wrote:
>
>> Perhaps to avoid duplication we could move to this and keep
>> Git-specific function in some other file.
>
> That would be fantastic! From a technical point of view, it would make
> a lot of sense to
On Tue, Jul 17, 2012 at 8:31 PM, Ævar Arnfjörð Bjarmason
wrote:
> Nice, I thought about doing something like this myself but never had the time.
Thanks. Took quite some time to take out the Git-specific
functionality. And there's still a lot of room for improvement.
> Perhaps to avoid duplicatio
On Tue, Jul 17, 2012 at 10:06 AM, Mathias Lafeldt
wrote:
> I've been wanting to announce Sharness [1] on this list for quite some
> time now, but never managed to do so. With the release of version
> 0.2.4, I think it's about time to change that.
>
> Sharness is a shell-based test harness library.
Hi,
I've been wanting to announce Sharness [1] on this list for quite some
time now, but never managed to do so. With the release of version
0.2.4, I think it's about time to change that.
Sharness is a shell-based test harness library. It was derived from
the Git project and is basically a genera
5 matches
Mail list logo
