On Tue, Jun 17, 2014 at 01:08:05PM +0200, Torsten Bögershausen wrote:
> On 2014-06-17 09.34, Jeremiah Mahler wrote:
> > Add a strnncmp() function which behaves like strncmp() except it takes
> > the length of both strings instead of just one.
> >
> > Then simplify tree-walk.c and unpack-trees.c us
On Thu, Jun 05, 2014 at 07:56:15PM -0400, David Turner wrote:
> Optimize check_refname_component using SSE4.2, where available.
>
> git rev-parse HEAD is a good test-case for this, since it does almost
> nothing except parse refs. For one particular repo with about 60k
> refs, almost all packed,
On Thu, Jun 05, 2014 at 02:30:17PM +0200, Torsten Bögershausen wrote:
> On 2014-06-04 23.16, David Turner wrote:
> >
> > Sure! I actually went with > 120k to make measurement easier:
> > https://github.com/dturner-tw/many-refs
> Hm, I didn't get so man
>
> git remote -v
> origin https://github.
On Mon, Mar 10, 2014 at 10:56:51AM -0700, David Lang wrote:
> On Mon, 10 Mar 2014, Ondřej Bílka wrote:
>
> >On Mon, Mar 10, 2014 at 03:13:45AM -0700, David Lang wrote:
> >>On Mon, 10 Mar 2014, Dennis Luehring wrote:
> >>
> >>>according to these blog posts
On Mon, Mar 10, 2014 at 03:13:45AM -0700, David Lang wrote:
> On Mon, 10 Mar 2014, Dennis Luehring wrote:
>
> >according to these blog posts
> >
> >http://www.infoq.com/news/2014/01/facebook-scaling-hg
> >https://code.facebook.com/posts/218678814984400/scaling-mercurial-at-facebook/
> >
> >mercuri
> 2013/10/26 Bryan Turner :
> > No, the .git/hooks directory in your clone is created from your local
> > templates, installed with your Git distribution, not the remote hooks.
> > On Linux distributions, these templates are often in someplace like
> > /usr/share/git-core/templates (for normal pack
On Mon, Oct 21, 2013 at 09:35:07AM -0700, Shawn Pearce wrote:
> On Mon, Oct 21, 2013 at 8:41 AM, wrote:
> > The change-id is exactly like a commit-id, it is an SHA-1 value, but it
> > is a constant embedded in the commit message.
>
> https://gerrit-review.googlesource.com/Documentation/user-chan
On Sun, Oct 20, 2013 at 08:27:13AM +0200, Torsten Bögershausen wrote:
> Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
> popelka.ms.mff.cuni.cz
> Status: O
> Content-Length: 2690
> Lines: 89
>
> On 20.10.13 08:05, Ondřej Bílka wrote:
> > On Sun, Oct 2
On Sun, Oct 20, 2013 at 07:47:06AM +0200, Torsten Bögershausen wrote:
> (may be s/path is too big/path is too long/ ?)
>
> On 19.10.13 12:52, Antoine Pelisse wrote:
> > Currently, most buffers created with PATH_MAX length, are not checked
> > when being written, and can overflow if PATH_MAX is not
On Wed, Sep 25, 2013 at 09:24:15AM +0200, Thomas Koch wrote:
> Is there any explanation available of the different merrits and drawbacks of
> the diff algorithms that Git supports?
>
> I'm not satisfied with the default diff but have enough processing power for
> a
> slower algorithm that might
On Mon, Jul 29, 2013 at 10:55:41AM -0400, Marc Branchaud wrote:
> On 13-07-29 04:18 AM, Ondřej Bílka wrote:
> > Hi,
> >
> > I improved my tool and it catched following additional typos.
> >
> > As with any big project best way to catch errors is to have aut
once instead for each person but I did not found suitable
workflow yet.
Signed-off-by: Ondřej Bílka
diff --git a/pathspec.c b/pathspec.c
index 6ea0867..27ffe77 100644
--- a/pathspec.c
+++ b/pathspec.c
@@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,
/*
* Finds
On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
> Ondřej Bílka writes:
>
> > If grepping random commit in history is important use case then keeping
> > db information in history makes sense. Otherwise just having database
> > for current version and u
On Thu, Jul 25, 2013 at 01:41:13PM -0700, Junio C Hamano wrote:
> Ondřej Bílka writes:
>
> > One solution would be to use same trick as was done in google code.
> > Build and keep database of trigraphs and which files contain how many of
> > them. When querry is made t
Hi,
When I do git grep then with big codebase (gcc) it executes slowly.
I am thinking to add option to speed up search time.
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made the
^ ^
- /* I hope we needn't fill ther regs with -1's when no match was
found. */
+ /* I hope we needn't fill their regs with -1's when no match was
found. */
^ ^
Signed-off-by: Ondřej Bílka
---
Docu
t; More majordomo info at http://vger.kernel.org/majordomo-info.html
Signed-off-by: Ondřej Bílka
---
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index e364007..fe723e4 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -4675,5 +4675,5 @@ Wr
On Sat, Jul 20, 2013 at 07:39:06PM +, brian m. carlson wrote:
> On Sat, Jul 20, 2013 at 09:13:12PM +0200, Ondřej Bílka wrote:
> > A dictionary that I generated is following, patch is below.
> >
> > alloted allocated
>
> "allotted" is a valid
On Sun, Jul 21, 2013 at 01:21:10AM +0530, Ramkumar Ramachandra wrote:
> Ondřej Bílka wrote:
> > diff --git a/builtin/checkout.c b/builtin/checkout.c
> > index 7fe0bff..9f29bb2 100644
> > --- a/builtin/checkout.c
> > +++ b/builtin/checkout.c
> > @@ -1137,7 +11
On Sun, Jul 21, 2013 at 01:00:11AM +0530, Ramkumar Ramachandra wrote:
> Ondřej Bílka wrote:
> > http://marc.theaimsgroup.com/?l=git&m=112927316408690&w=2
>
> Just run a sed 's|http://marc.theaimsgroup.com|http://marc.info|', and
> submit the resulting patch.
Hi, I ran simple script to check for dead links. It found three false
positives and following link that now looks defunct.
What we do about it?
http://marc.theaimsgroup.com/?l=git&m=112927316408690&w=2
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
Hi, I wrote a tool that effectively fixes typos in comments and only in
comments.
It can be downloaded here:
https://github.com/neleai/stylepp
Now I fix specific typos. First I need to generate list of likely typos.
This is done by running following commands in desired directory
STYLEPP/script/
Hi, I wrote a tool that effectively fixes typos in comments and only in
comments.
It can be downloaded here:
https://github.com/neleai/stylepp
For typos you need identify them, write replacement dictionary and run
STYLEPP/script/stylepp_skeleton stylepp_fix_comment
Here generic dictionary is use
23 matches
Mail list logo
