Re: What's cooking in git.git (Mar 2014, #01; Tue, 4)

2014-03-13 Thread Jeff King
On Wed, Mar 12, 2014 at 07:55:51PM +0700, Duy Nguyen wrote:

 On Wed, Mar 5, 2014 at 7:10 AM, Junio C Hamano gits...@pobox.com wrote:
  [Graduated to master]
  * jk/pack-bitmap (2014-02-12) 26 commits
(merged to 'next' on 2014-02-25 at 5f65d26)
 
 And it's finally in! Shall we start thinking about the next on-disk
 format? It was put aside last time to focus on getting this series in.
 My concern is shallow support (surprise?) so that cloning from a
 1-year-long shallow repo is not slower than a complete one. An
 extensible format is enough without going into details.

I'm open to suggestions. The most interesting followups for me are:

  1. Taking a look at Karsten's hashmap patches, which also graduated
 recently, to see if we can drop khash's macro nastiness without
 losing performance.

  2. Can we use bitmaps to increase our idea of which objects the other
 side has, and therefore get better delta reuse? I think the answer
 is yes from my limited experiments, but I want to do some more
 thorough ones[1].

  3. Cleaning up and submitting my patches to avoid writing deltas
 between distinct ref sets (e.g., between refs for two different
 forks in an alternates repo). This is somewhat orthogonal to
 bitmaps, but they touch overlapping areas, so I had held back until
 the dust settled on bitmaps.

  4. Packv4. :)

  5. Short of packv4, looking at whether we can encoding packv2 tree
 deltas in a way that lets us produce cheap tree diffs in a high
 percentage of instances. This may sound crazy, as packv4 is a
 better endgame, but there is going to be a long time where packv2
 is still the on-the-wire format, which means that servers will need
 to do v4-to-v2 translation, which I suspect may eliminate the v4
 benefits.

Shallow repos aren't really on my radar (nor am I really familiar with
some of the intricacies), but I'm happy to discuss and give my
ill-informed opinions. :)

[1] http://thread.gmane.org/gmane.comp.version-control.git/239647
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: What's cooking in git.git (Mar 2014, #01; Tue, 4)

2014-03-12 Thread Duy Nguyen
On Wed, Mar 5, 2014 at 7:10 AM, Junio C Hamano gits...@pobox.com wrote:
 [Graduated to master]
 * jk/pack-bitmap (2014-02-12) 26 commits
   (merged to 'next' on 2014-02-25 at 5f65d26)

And it's finally in! Shall we start thinking about the next on-disk
format? It was put aside last time to focus on getting this series in.
My concern is shallow support (surprise?) so that cloning from a
1-year-long shallow repo is not slower than a complete one. An
extensible format is enough without going into details.
-- 
Duy
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: What's cooking in git.git (Mar 2014, #01; Tue, 4)

2014-03-10 Thread Johannes Sixt
Am 3/5/2014 1:10, schrieb Junio C Hamano:
 * nd/gitignore-trailing-whitespace (2014-02-10) 2 commits
  - dir: ignore trailing spaces in exclude patterns
  - dir: warn about trailing spaces in exclude patterns
 
  Warn and then ignore trailing whitespaces in .gitignore files,
  unless they are quoted for fnmatch(3), e.g. path\ .
 
  Will merge to 'next'.

The new test does not pass on Windows. I'll attempt to prepare patches
that amount to work around using FUNNYNAMES, but I'm running out of time now.

-- Hannes
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: What's cooking in git.git (Mar 2014, #01; Tue, 4)

2014-03-10 Thread Junio C Hamano
Johannes Sixt j.s...@viscovery.net writes:

 Am 3/5/2014 1:10, schrieb Junio C Hamano:
 * nd/gitignore-trailing-whitespace (2014-02-10) 2 commits
  - dir: ignore trailing spaces in exclude patterns
  - dir: warn about trailing spaces in exclude patterns
 
  Warn and then ignore trailing whitespaces in .gitignore files,
  unless they are quoted for fnmatch(3), e.g. path\ .
 
  Will merge to 'next'.

 The new test does not pass on Windows.

Thanks, will mark not to merge to 'master' yet.


--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html