All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2014, #03; Fri, 11)
Date: Sun, 13 Apr 2014 22:18:32 +0200	[thread overview]
Message-ID: <534AF118.5040501@alum.mit.edu> (raw)
In-Reply-To: <xmqq1tx3qzel.fsf@gitster.dls.corp.google.com>

On 04/12/2014 12:22 AM, Junio C Hamano wrote:
> [...]
> * mh/ref-transaction (2014-04-07) 27 commits
>  - ref_transaction_commit(): work with transaction->updates in place
>  - struct ref_update: add a type field
>  - struct ref_update: add a lock field
>  - ref_transaction_commit(): simplify code using temporary variables
>  - struct ref_update: store refname as a FLEX_ARRAY
>  - struct ref_update: rename field "ref_name" to "refname"
>  - refs: remove API function update_refs()
>  - update-ref --stdin: reimplement using reference transactions
>  - refs: add a concept of a reference transaction
>  - update-ref --stdin: harmonize error messages
>  - update-ref --stdin: improve the error message for unexpected EOF
>  - t1400: test one mistake at a time
>  - update-ref --stdin -z: deprecate interpreting the empty string as zeros
>  - update-ref.c: extract a new function, parse_next_sha1()
>  - t1400: test that stdin -z update treats empty <newvalue> as zeros
>  - update-ref --stdin: simplify error messages for missing oldvalues
>  - update-ref --stdin: make error messages more consistent
>  - update-ref --stdin: improve error messages for invalid values
>  - update-ref.c: extract a new function, parse_refname()
>  - parse_cmd_verify(): copy old_sha1 instead of evaluating <oldvalue> twice
>  - update-ref --stdin: read the whole input at once
>  - update_refs(): fix constness
>  - refs.h: rename the action_on_err constants
>  - t1400: add some more tests involving quoted arguments
>  - parse_arg(): really test that argument is properly terminated
>  - t1400: provide more usual input to the command
>  - t1400: fix name and expected result of one test
>  (this branch is used by rs/ref-closer-to-atomic.)
> 
>  Update "update-ref --stdin [-z]" and then introduce a transactional
>  support for (multi-)reference updates.
> 
>  Is this ready to be merged to 'next' for wider exposure?

Yes, as far as I know there are no outstanding objections to this
version (v3) of this series and it is ready for 'next'.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  parent reply	other threads:[~2014-04-13 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 22:22 What's cooking in git.git (Apr 2014, #03; Fri, 11) Junio C Hamano
2014-04-11 23:27 ` Felipe Contreras
2014-04-12  6:49   ` Junio C Hamano
2014-04-12 18:29 ` Ramsay Jones
2014-04-15 16:45   ` Junio C Hamano
2014-04-15 23:18     ` Duy Nguyen
2014-04-16 11:31       ` Ramsay Jones
2014-04-13 20:18 ` Michael Haggerty [this message]
2014-04-17 16:52 ` W. Trevor King
2014-04-17 17:52   ` Junio C Hamano

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=534AF118.5040501@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.