On Fri, 2018-05-11 at 11:31 +0200, Michael Haggerty wrote:
> On Wed, May 9, 2018 at 4:33 PM, Christian Couder
> wrote:
> > I might start working on implementing reftable in Git soon.
> > [...]
>
> Nice. It'll be great to have a reftable implementation in git core
> (and ideally libgit2, as well).
On Wed, May 9, 2018 at 4:33 PM, Christian Couder
wrote:
> I might start working on implementing reftable in Git soon.
> [...]
Nice. It'll be great to have a reftable implementation in git core
(and ideally libgit2, as well). It seems to me that it could someday
become the new default reference st
On Wed, May 09 2018, Stefan Beller wrote:
> Hi Christian,
>
> On Wed, May 9, 2018 at 7:33 AM, Christian Couder
> wrote:
>> Hi,
>>
>> I might start working on implementing reftable in Git soon.
>
> Cool! Everyone is waiting for it as they dream about the
> performance and correctness benefits thi
On Wed, 2018-05-09 at 10:54 -0700, Jonathan Nieder wrote:
> Carlos Martín Nieto wrote:
> > On Wed, 2018-05-09 at 09:48 -0700, Jonathan Nieder wrote:
> > > If you would like the patches at https://git.eclipse.org/r/q/topi
> > > c:reftable
> > > relicensed for Git's use so that you don't need to incl
On Wed, May 9, 2018 at 10:48 AM, Jonathan Nieder wrote:
> Stefan Beller wrote:
>
>> * We *might* be able to use reftables in negotiation later
>> ("client: Last I fetched, you said your latest transaction
>> number was '5' with the hash over all refs to be ;
>> server: ok, here are the refs
Carlos Martín Nieto wrote:
> On Wed, 2018-05-09 at 09:48 -0700, Jonathan Nieder wrote:
>> If you would like the patches at https://git.eclipse.org/r/q/topic:reftable
>> relicensed for Git's use so that you don't need to include that
>> license header, let me know. Separate from any legal concerns
Hi all,
On Wed, 2018-05-09 at 09:48 -0700, Jonathan Nieder wrote:
> Hi,
>
> Christian Couder wrote:
>
> > I might start working on implementing reftable in Git soon.
>
> Yay!
>
> [...]
> > So I think the most straightforward and compatible way to do it would
> > be to port the JGit implementat
Stefan Beller wrote:
> * We *might* be able to use reftables in negotiation later
> ("client: Last I fetched, you said your latest transaction
> number was '5' with the hash over all refs to be ;
> server: ok, here are the refs and the pack, you're welcome").
Do you mean that reftable's ref
Hi Christian,
On Wed, May 9, 2018 at 7:33 AM, Christian Couder
wrote:
> Hi,
>
> I might start working on implementing reftable in Git soon.
Cool! Everyone is waiting for it as they dream about the
performance and correctness benefits this brings.
Benefits that I know of:
* performance in repos
Hi,
Christian Couder wrote:
> I might start working on implementing reftable in Git soon.
Yay!
[...]
> So I think the most straightforward and compatible way to do it would
> be to port the JGit implementation.
I suspect following the spec[1] would be even more compatible, since it
would force
On Wed, May 9, 2018 at 4:33 PM, Christian Couder
wrote:
> Hi,
>
> I might start working on implementing reftable in Git soon.
Adding Michael Haggerty who did lots of work on ref stuff. He probably
can give a few suggestions.
You probably should also look at the last attempt to add lmdb as a new
On 5/9/2018 10:33 AM, Christian Couder wrote:
Hi,
I might start working on implementing reftable in Git soon.
During the last Git Merge conference last March Stefan talked about
reftable. In Alex Vandiver's notes [1] it is asked that people
announce it on the list when they start working on it,
12 matches
Mail list logo
