Trac does not display the "last 10 new commits"

[Nathann Cohen]

Hellooooooooooooo !!!

Just a small thing : when a branch is pushed trac does not exactly
print the last 10 commits, but the first 10 which do not belong to
develop.

#15681 contains only one commit, but has #15623 as a dependency.
Aaaaaaaaand well, no commit of #15681 appears on its ticket ^^;

Nathann

[R. Andrew Ohana]

On Wed, Jan 15, 2014 at 2:20 AM, Nathann Cohen <nathan...@gmail.com> wrote:

Hellooooooooooooo !!!

Just a small thing : when a branch is pushed trac does not exactly
print the last 10 commits, but the first 10 which do not belong to
develop.

Yes, this is on purpose. I think I use the phrasing "new commits", because I don't consider
those in the develop branch to be new (they have already been positively reviewed and
tested on the buildbots). Also, in almost all cases, these commits aren't relevant to the ticket
in question, so all these extra commits would do would be cluttering up the ticket and
obfuscating the relevant commits.

 

#15681 contains only one commit, but has #15623 as a dependency.
Aaaaaaaaand well, no commit of #15681 appears on its ticket ^^;

I don't really understand what you mean by this.

 

Nathann

--
You received this message because you are subscribed to the Google Groups "sage-git" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-git+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Andrew

[Nathann Cohen]

Hello !

Here is what I meant :

- I have a ticket A with 15 commits on top on the developer branch

- I have a ticket B based on A with one commit

- when I push my branch B containing 16 commits, I only see the FIRST (not last) 10 commits of the branch, and all of them belong to A. The only commit which belongs to B, the 16th, is not displayed.

Nathann