All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: What's cooking in git.git (Jun 2016, #10; Wed, 29)
Date: Thu, 30 Jun 2016 01:56:11 +0100	[thread overview]
Message-ID: <57746E2B.4000303@ramsayjones.plus.com> (raw)
In-Reply-To: <xmqqd1mz1sxd.fsf@gitster.mtv.corp.google.com>



On 30/06/16 00:22, Junio C Hamano wrote:
[snip]
> 
> * mh/ref-store (2016-06-20) 38 commits
>  - refs: implement iteration over only per-worktree refs
>  - refs: make lock generic
>  - refs: add method to rename refs
>  - refs: add methods to init refs db
>  - refs: make delete_refs() virtual
>  - refs: add method for initial ref transaction commit
>  - refs: add methods for reflog
>  - refs: add method iterator_begin
>  - files_ref_iterator_begin(): take a ref_store argument
>  - split_symref_update(): add a files_ref_store argument
>  - lock_ref_sha1_basic(): add a files_ref_store argument
>  - lock_ref_for_update(): add a files_ref_store argument
>  - commit_ref_update(): add a files_ref_store argument
>  - lock_raw_ref(): add a files_ref_store argument
>  - repack_without_refs(): add a files_ref_store argument
>  - refs: make peel_ref() virtual
>  - refs: make create_symref() virtual
>  - refs: make pack_refs() virtual
>  - refs: make verify_refname_available() virtual
>  - refs: make read_raw_ref() virtual
>  - resolve_gitlink_ref(): rename path parameter to submodule
>  - resolve_gitlink_ref(): avoid memory allocation in many cases
>  - resolve_gitlink_ref(): implement using resolve_ref_recursively()
>  - resolve_ref_recursively(): new function
>  - read_raw_ref(): take a (struct ref_store *) argument
>  - resolve_gitlink_packed_ref(): remove function
>  - resolve_packed_ref(): rename function from resolve_missing_loose_ref()
>  - refs: reorder definitions
>  - refs: add a transaction_commit() method
>  - {lock,commit,rollback}_packed_refs(): add files_ref_store arguments
>  - resolve_missing_loose_ref(): add a files_ref_store argument
>  - get_packed_ref(): add a files_ref_store argument
>  - add_packed_ref(): add a files_ref_store argument
>  - refs: create a base class "ref_store" for files_ref_store
>  - refs: add a backend method structure
>  - refs: rename struct ref_cache to files_ref_store
>  - rename_ref_available(): add docstring
>  - resolve_gitlink_ref(): eliminate temporary variable
>  (this branch uses mh/ref-iterators and mh/split-under-lock; is tangled with mh/update-ref-errors.)
> 
>  The ref-store abstraction was introduced to the refs API so that we
>  can plug in different backends to store references.
> 
>  Is everybody happy with this version?
>  If so, will merge to 'next'.

A small fixup required for this one.

see http://thread.gmane.org/gmane.comp.version-control.git/298137

ATB,
Ramsay Jones




      reply	other threads:[~2016-06-30  0:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 23:22 What's cooking in git.git (Jun 2016, #10; Wed, 29) Junio C Hamano
2016-06-30  0:56 ` Ramsay Jones [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57746E2B.4000303@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.