From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Jeff King <peff@peff.net>,
Ernesto Maserati <ernesto.2.maserati@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: How to generate feature branch statistics?
Date: Wed, 20 Jul 2016 16:31:04 -0700 [thread overview]
Message-ID: <CAPc5daUjK1k8teTw8enb3yNwo+WesJY3BVHM34Wdqu31czUB4Q@mail.gmail.com> (raw)
In-Reply-To: <579004CC.8090503@gmail.com>
On Wed, Jul 20, 2016 at 4:10 PM, Jakub Narębski <jnareb@gmail.com> wrote:
> W dniu 2016-07-20 o 20:49, Junio C Hamano pisze:
>
>> For our own history and workflow, the duration between the inception
>> of a topic branch and the time it gets merged to 'master' is not all
>> that interesting.
>
> Nb. if I haven't messed something up (the git history is not simple
> merging of topic branches into mainline), the shortest time from
> creating a branch to merging it in git.git is 7 seconds (probably
> it was a bugfix-type of a topic branch), the longest if I did it
> correctly is slightly less than 4 years (???): 641830c.
The former is quite understandable. The point of having such a topic
is so that it can be merged down to older maintenance releases.
next prev parent reply other threads:[~2016-07-20 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:05 How to generate feature branch statistics? Ernesto Maserati
2016-07-20 13:14 ` Jeff King
2016-07-20 18:49 ` Junio C Hamano
2016-07-20 23:10 ` Jakub Narębski
2016-07-20 23:31 ` Junio C Hamano [this message]
2016-07-20 13:56 ` Jakub Narębski
2016-07-20 18:10 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPc5daUjK1k8teTw8enb3yNwo+WesJY3BVHM34Wdqu31czUB4Q@mail.gmail.com \
--to=gitster@pobox.com \
--cc=ernesto.2.maserati@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).