git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] refs.c: write updates to packed refs when a transaction has more than one ref

From
Ronnie Sahlberg <sahlberg@google.com>
Date
Jun 9, 2014, 16:20 UTC
Message-ID
<CAL=YDWk+KsctVnLMFv6tWC-=Z6uAaTbYLnJJUyBaY+yxwmM7Mw@mail.gmail.com>
In-Reply-To
<CAPig+cTQocaZBHciFkP591A11w9qcKAvG5a2H+R=7QHVvxU4EQ@mail.gmail.com>
thanks
On Sun, Jun 8, 2014 at 2:03 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 10 quoted lines
> On Thu, Jun 5, 2014 at 7:26 PM, Ronnie Sahlberg <sahlberg@google.com> wrote:
>> When we are updating more than one single ref, i.e. not a commit, then
>> write the updated refs directly to the packed refs file instead of writing
>> them as loose refs.
>>
>> Change clone to use a transaction instead of using the pacekd refs api.
>
> s/pacekd/packed/
>
>> Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
Previous: Eric SunshineNext: Ronnie Sahlberg
Message 4 of 5 in “Write multi-ref updates directly to packed refs”
  1. 0/2 Write multi-ref updates directly to packed refsRonnie Sahlberg, Jun 5, 2014
  2. 1/2 refs.c: write updates to packed refs when a transaction has more than one refRonnie Sahlberg, Jun 5, 2014
  3. Eric SunshineJun 8, 2014
  4. Ronnie SahlbergJun 9, 2014
  5. 2/2 refs.c: make the *_packed_refs functions staticRonnie Sahlberg, Jun 5, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.