On 2019-04-08 21:36, Matheus Tavares Bernardino wrote:
> On Mon, Apr 8, 2019 at 4:19 PM Philip Oakley wrote:
>>
>> Hi Matheus
>>
>> On 08/04/2019 18:04, Matheus Tavares Bernardino wrote:
Another "32-bit problem" should also be expressly considered during the
GSoC work because of the MS W
On Mon, Apr 8, 2019 at 4:19 PM Philip Oakley wrote:
>
> Hi Matheus
>
> On 08/04/2019 18:04, Matheus Tavares Bernardino wrote:
> >> Another "32-bit problem" should also be expressly considered during the
> >> GSoC work because of the MS Windows definition of uInt / long to be only
> >> 32 bits, lea
Hi Matheus
On 08/04/2019 18:04, Matheus Tavares Bernardino wrote:
Another "32-bit problem" should also be expressly considered during the
GSoC work because of the MS Windows definition of uInt / long to be only
32 bits, leading to much of the Git code failing on the Git for Windows
port and on t
On Mon, Apr 8, 2019 at 6:26 AM Philip Oakley wrote:
>
> On 08/04/2019 02:23, Duy Nguyen wrote:
> > On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
> > wrote:
> >>> Git has a very optimized mechanism to compactly store
> >>> objects (blobs, trees, commits, etc.) in packfiles[2]. These files are
>
On Sun, Apr 7, 2019 at 7:52 PM Christian Couder
wrote:
>
> Hi Matheus
>
> On Sun, Apr 7, 2019 at 10:48 PM Matheus Tavares Bernardino
> wrote:
> >
> > This is my proposal for GSoC with the subject "Make pack access code
> > thread-safe".
>
> Thanks!
>
> > I'm late in schedule but I would like to a
On Mon, Apr 8, 2019 at 3:58 AM Christian Couder
wrote:
>
> On Mon, Apr 8, 2019 at 5:32 AM Duy Nguyen wrote:
> >
> > On Mon, Apr 8, 2019 at 8:23 AM Duy Nguyen wrote:
> > >
> > > On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
> > > wrote:
> > > > > Git has a very optimized mechanism to compactly
On Mon, Apr 8, 2019 at 12:32 AM Duy Nguyen wrote:
>
> On Mon, Apr 8, 2019 at 8:23 AM Duy Nguyen wrote:
> >
> > On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
> > wrote:
> > > > Git has a very optimized mechanism to compactly store
> > > > objects (blobs, trees, commits, etc.) in packfiles[2]. T
On 08/04/2019 02:23, Duy Nguyen wrote:
On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
wrote:
Git has a very optimized mechanism to compactly store
objects (blobs, trees, commits, etc.) in packfiles[2]. These files are
created by[3]:
1. listing objects;
2. sorting the list with some good heuri
On Mon, Apr 8, 2019 at 5:32 AM Duy Nguyen wrote:
>
> On Mon, Apr 8, 2019 at 8:23 AM Duy Nguyen wrote:
> >
> > On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
> > wrote:
> > > > Git has a very optimized mechanism to compactly store
> > > > objects (blobs, trees, commits, etc.) in packfiles[2]. Th
On Mon, Apr 8, 2019 at 8:23 AM Duy Nguyen wrote:
>
> On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
> wrote:
> > > Git has a very optimized mechanism to compactly store
> > > objects (blobs, trees, commits, etc.) in packfiles[2]. These files are
> > > created by[3]:
> > >
> > > 1. listing object
On Mon, Apr 8, 2019 at 5:52 AM Christian Couder
wrote:
> > Git has a very optimized mechanism to compactly store
> > objects (blobs, trees, commits, etc.) in packfiles[2]. These files are
> > created by[3]:
> >
> > 1. listing objects;
> > 2. sorting the list with some good heuristics;
> > 3. trave
Hi Matheus
On Sun, Apr 7, 2019 at 10:48 PM Matheus Tavares Bernardino
wrote:
>
> This is my proposal for GSoC with the subject "Make pack access code
> thread-safe".
Thanks!
> I'm late in schedule but I would like to ask for your
> comments on it. Any feedback will be highly appreciated.
>
> Th
Hi, everyone
This is my proposal for GSoC with the subject "Make pack access code
thread-safe". I'm late in schedule but I would like to ask for your
comments on it. Any feedback will be highly appreciated.
The "rendered" version can be seen here:
https://docs.google.com/document/d/1QXT3iiI5zjwus
13 matches
Mail list logo