onsdag 20 maj 2009 23:43:59 skrev "Shawn O. Pearce" <spearce@xxxxxxxxxxx>:
> Robin Rosenberg <robin.rosenberg@xxxxxxxxxx> wrote:
> > Also adds a few some more test for refs, though not complete.
>
> Hmm, tests fail, wrong expected values?
Gah, not sure how that passed. It's not random failures...
> Actual was Result.REJECTED_CURRENT_BRANCH.
>
> > @@ -349,12 +355,20 @@ private synchronized Ref readRefBasic(final String origName,
> > +
> > + if (!origName.equals(name)) {
> > + ref = new Ref(Ref.Storage.LOOSE, origName, name, id);
> > + looseRefs.put(origName, ref);
> > + }
>
> Seems fine, but I'm starting to hate our current way of handling
> symrefs. Not for this series. But its starting to worry me.
I agree. For decorating the history it's convenient, but it's inconsistent. For some reason
it was harder to see without the unit tests. All kinds of things slip by when testing is
done on the surface only.
I'll update, and and even more tests.
Should we use multiple Ref objects for symrefs? I.e. a Ref referring to another in a chain,
with all symrefs in between visible?
-- robin
--
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