4 ms·
cool idea, how far back (in time) do those 27k commits go? Just thinking how this could maybe used for (automated) research / visualization on the evolution of
by 7777777phil 7mo ago
cool idea, how far back (in time) do those 27k commits go?
Just thinking how this could maybe used for (automated) research / visualization on the evolution of (spanish - in this case) law
- codethief 7mo ago> how far back (in time) do those 27k commits go Looking at the commit dates (which seem to be derived from the original publication dates) the history seems quite sparse/incomplete(?) I mean, there have only been 26 commits since 2000.
- Meneth 7mo agoIt seems the commits aren't in proper date order. Here are some newer changes, placed before the latest commits: https://github.com/EnriqueLop/legalize-es/commits/master/?after=1d6c96ca4d632e1660bf6dd9661f045eadd814e0+104 https://github.com/EnriqueLop/legalize-es/commits/master/?af...
- forgotpwd16 7mo agoIt's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata. So commits 1->2->3->4 could be modified to have timestamps 1->3->2->4. I know GitHub prefers sorting with author over commit date, but don't know how topology is handled.
- codethief 7mo ago> It's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata. Yeah, I think everyone is aware. It's just that the last couple dozen commits, to me, looked like commits had been created in chronological order, so that topological order == chronological order. > I know GitHub prefers sorting with author over commit date, but don't know how topology is handled. Commits are usually sorted topologically.