You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vxquery.apache.org by Marvin Humphrey <ma...@rectangular.com> on 2014/02/26 22:53:57 UTC
Re: [11/25] git commit: This commit holds three ideas: local
partitioning, reusing the parser per runtime, and optimizations for child
path step. Since all these activities deal with VXQueryCollectionOperatorDescriptor
and they are code change I am pulling f
Hi,
On Sun, Feb 23, 2014 at 5:42 PM, <pr...@apache.org> wrote:
> This commit holds three ideas: local partitioning, reusing the parser per runtime, and optimizations for child path step.
> Since all these activities deal with VXQueryCollectionOperatorDescriptor and they are code change I am pulling from another branch, I have just kept them in this one commit.
Maybe consider this excerpt from `git help commit` about formulating commit
messages.
DISCUSSION
Though not required, it's a good idea to begin the commit message with
a single short (less than 50 character) line summarizing the change,
followed by a blank line and then a more thorough description. Tools
that turn commits into email, for example, use the first line on the
Subject: line and the rest of the commit in the body.
HTH,
Marvin Humphrey
Re: [11/25] git commit: This commit holds three ideas: local
partitioning, reusing the parser per runtime, and optimizations for child
path step. Since all these activities deal with VXQueryCollectionOperatorDescriptor
and they are code change I am pulling f
Posted by Eldon Carman <ec...@ucr.edu>.
Thanks for the tip. I will start using this convention.
Preston
On Wed, Feb 26, 2014 at 1:53 PM, Marvin Humphrey <ma...@rectangular.com>wrote:
> Hi,
>
> On Sun, Feb 23, 2014 at 5:42 PM, <pr...@apache.org> wrote:
> > This commit holds three ideas: local partitioning, reusing the parser
> per runtime, and optimizations for child path step.
> > Since all these activities deal with VXQueryCollectionOperatorDescriptor
> and they are code change I am pulling from another branch, I have just kept
> them in this one commit.
>
> Maybe consider this excerpt from `git help commit` about formulating commit
> messages.
>
> DISCUSSION
>
> Though not required, it's a good idea to begin the commit message
> with
> a single short (less than 50 character) line summarizing the change,
> followed by a blank line and then a more thorough description. Tools
> that turn commits into email, for example, use the first line on the
> Subject: line and the rest of the commit in the body.
>
> HTH,
>
> Marvin Humphrey
>