Tue, 25 Jan 2011 18:12:35 -0500, Darren Dale wrote:
[clip]
> Pauli: could I trouble you to have a look at my rules file, maybe you
> will notice something I overlooked?
> (https://github.com/darrendale/mpl2git/blob/master/matplotlib.rules) Any
> other ideas?
As an additional check, I'd suggest checking that the history graph
in each repository is simple. Find all root (parentless) commits:
git rev-list --parents master | egrep "^[a-f0-9]{40}$" # for master branch
git rev-list --parents --all | egrep "^[a-f0-9]{40}$" # all branches
There should be only one root commit, unless there is a very good
reason to have several.
If there are multiple root commits, this may indicate that
the history was splintered into several parts (e.g. due to complicated
SVN moves), which needs manual grafting to connect the parts.
For perfectionists, I'd also suggest eyeballing the "gitk --all" DAG.
--
Pauli Virtanen
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
