#3421: Changeset Consolidation.
----------------------------+-----------------------------------------------
Reporter: volte | Owner: cboos
Type: enhancement | Status: new
Priority: normal | Milestone: 0.11
Component: changeset view | Version: 0.9.6
Severity: minor | Resolution:
Keywords: |
----------------------------+-----------------------------------------------
Changes (by cboos):
* milestone: => 0.11
* owner: jonas => cboos
Old description:
> I've noticed in the timeline view, that people upload (check in) multiple
> times quite often within minutes, even seconds of their previous check
> in. Was wondering how hard it would be to add the ability to tree those.
> By that I mean, group together adjacent check ins by the same user under
> the latest one of theirs. For example.
>
> 22:02 Changeset [1536] by userNumber1
> 22:01 Changeset [1535] by userNumber1
> 22:00 Changeset [1534] by userNumber1
> 21:59 Changeset [1533] by userNumber1
> 21:58 Changeset [1532] by userNumber1
> 21:56 Changeset [1531] by userNumber1
> 21:49 Changeset [1530] by userNumber1
> 21:48 Changeset [1529] by userNumber1
> 21:47 Changeset [1528] by userNumber1
> 21:27 Changeset [1527] by userNumber2
> 21:22 Changeset [1523] by userNumber1
> 21:20 Changeset [1522] by userNumber1
> 21:19 Changeset [1521] by userNumber1
>
> Would become:
> 22:02 Changeset [1536] by userNumber1
> 21:27 Changeset [1527] by userNumber2
> 21:22 Changeset [1523] by userNumber1
>
> With both userNumber1 Changesets being able to expand a list of the
> adjacent changesets. Does that make sense? Just a little enhancement that
> would unclutter the timeline page :)
>
> Of if it already exists (which I couldn't find, sorry if it does) tell me
> how to do so :)
>
> Cheers.
New description:
I've noticed in the timeline view, that people upload (check in) multiple
times quite often within minutes, even seconds of their previous check in.
Was wondering how hard it would be to add the ability to tree those. By
that I mean, group together adjacent check ins by the same user under the
latest one of theirs. For example.
{{{
22:02 Changeset [1536] by userNumber1
22:01 Changeset [1535] by userNumber1
22:00 Changeset [1534] by userNumber1
21:59 Changeset [1533] by userNumber1
21:58 Changeset [1532] by userNumber1
21:56 Changeset [1531] by userNumber1
21:49 Changeset [1530] by userNumber1
21:48 Changeset [1529] by userNumber1
21:47 Changeset [1528] by userNumber1
21:27 Changeset [1527] by userNumber2
21:22 Changeset [1523] by userNumber1
21:20 Changeset [1522] by userNumber1
21:19 Changeset [1521] by userNumber1
}}}
Would become:
{{{
22:02 Changeset [1536] by userNumber1
21:27 Changeset [1527] by userNumber2
21:22 Changeset [1523] by userNumber1
}}}
With both userNumber1 Changesets being able to expand a list of the
adjacent changesets. Does that make sense? Just a little enhancement that
would unclutter the timeline page :)
Of if it already exists (which I couldn't find, sorry if it does) tell me
how to do so :)
Cheers.
Comment:
Interesting idea. The consolidation could be made if the author and
comment
remains the same across successive commits. Then the resulting timeline
event
could be the revision ''range'' i.e.
{{{
22:02 Changesets [1528:1536] by userNumber1
21:27 Changeset [1527] by userNumber2
21:22 Changesets [1521:1523] by userNumber1
}}}
The link should then lead to the Changeset view corresponding to that
range.
--
Ticket URL: <http://trac.edgewall.org/ticket/3421>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
