Re: [PATCH v3 18/24] read-cache: write index-v5

2013-11-25 Thread Thomas Gummerer
[sorry about taking so much time to get back to you, was too busy with other stuff to work on git] Duy Nguyen writes: > On Mon, Aug 19, 2013 at 2:42 AM, Thomas Gummerer wrote: >> +char *super_directory(const char *filename) >> +{ >> + char *slash; >> + >> + slash = strrchr(filename

Re: [PATCH v3 18/24] read-cache: write index-v5

2013-08-24 Thread Duy Nguyen
On Sat, Aug 24, 2013 at 11:07 AM, Duy Nguyen wrote: > On Mon, Aug 19, 2013 at 2:42 AM, Thomas Gummerer wrote: >> Write the index version 5 file format to disk. This version doesn't >> write the cache-tree data and resolve-undo data to the file. > > I keep having things to add after sending my ema

Re: [PATCH v3 18/24] read-cache: write index-v5

2013-08-23 Thread Duy Nguyen
On Mon, Aug 19, 2013 at 2:42 AM, Thomas Gummerer wrote: > Write the index version 5 file format to disk. This version doesn't > write the cache-tree data and resolve-undo data to the file. I keep having things to add after sending my emails. Now that we have all conflicted entries in file block,

Re: [PATCH v3 18/24] read-cache: write index-v5

2013-08-23 Thread Duy Nguyen
On Mon, Aug 19, 2013 at 2:42 AM, Thomas Gummerer wrote: > +char *super_directory(const char *filename) > +{ > + char *slash; > + > + slash = strrchr(filename, '/'); > + if (slash) > + return xmemdupz(filename, slash-filename); > + return NULL; > +} > + Why is

[PATCH v3 18/24] read-cache: write index-v5

2013-08-18 Thread Thomas Gummerer
Write the index version 5 file format to disk. This version doesn't write the cache-tree data and resolve-undo data to the file. The main work is done when filtering out the directories from the current in-memory format, where in the same turn also the conflicts and the file data is calculated. H