github commit query

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

github commit query

Paul Franklin-5
Should I care that some recent commits (as reported by
github.com/orgs/gramps-project/dashboard) say things
like "158 commits" and "171 commits"?

Thanks.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: github commit query

John Ralls-2

> On May 10, 2015, at 3:29 PM, Paul Franklin <[hidden email]> wrote:
>
> Should I care that some recent commits (as reported by
> github.com/orgs/gramps-project/dashboard) say things
> like "158 commits" and "171 commits"?

Paul,

Whether you care or not is up to you, but you needn’t necessarily be concerned: That message is normal when one does a merge: All of the commits in the “source” branch are added by reference to the “target” branch.

In the case of PR 21, the merge was a bit unfortunate, because Ross somehow managed to create a feature branch from master’s head and then merged in a different version of master in which he appears to have re-committed everything between 7cb69fa and f4f83e4. It doesn’t have an effect on the state of the code, but it does make history look pretty ugly. He apparently made an even worse version of the same mistake in PR #20 but recognized it that time and killed the PR.

Regards,
John Ralls


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: github commit query

DS Blank
In reply to this post by Paul Franklin-5
On Sun, May 10, 2015 at 6:29 PM, Paul Franklin <[hidden email]> wrote:
Should I care that some recent commits (as reported by
github.com/orgs/gramps-project/dashboard) say things
like "158 commits" and "171 commits"?

The dashboard shows a variety of activities, including pull requests that are made, and then closed. One of the large commits was closed, and the other was merged. If you look at the merge, only one file was changed. That was a particularly tricky set of changes to work with. In the end, it may have been easier to just make that change independent of the original set of changes.

The good news is that we have more people helping with gramps development.

-Doug
 

Thanks.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: github commit query

Ross Gammon
In reply to this post by John Ralls-2
On 05/11/2015 01:14 AM, John Ralls wrote:

>
> In the case of PR 21, the merge was a bit unfortunate, because Ross somehow managed to create a feature branch from master’s head and then merged in a different version of master in which he appears to have re-committed everything between 7cb69fa and f4f83e4. It doesn’t have an effect on the state of the code, but it does make history look pretty ugly. He apparently made an even worse version of the same mistake in PR #20 but recognized it that time and killed the PR.
>

I found a good way to waste an hour or so on a weekend when it should
only have taken 15 mins :-)

Next time I hope it will be cleaner.


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

signature.asc (836 bytes) Download Attachment