On 04/01/2014 09:39 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>
>> Build out the API for dealing with a bunch of reference checks and
>> changes within a transaction. Define an opaque ref_transaction type
>> that is managed entirely within refs.c. Introduce functions for
>> beginning
Michael Haggerty writes:
> Build out the API for dealing with a bunch of reference checks and
> changes within a transaction. Define an opaque ref_transaction type
> that is managed entirely within refs.c. Introduce functions for
> beginning a transaction, adding updates to a transaction, and
>
On 03/26/2014 07:39 PM, Brad King wrote:
> On 03/24/2014 01:56 PM, Michael Haggerty wrote:
>> +void ref_transaction_update(struct ref_transaction *transaction,
>> +const char *refname,
>> +unsigned char *new_sha1, unsigned char *old_sha1,
>> +
On 03/24/2014 01:56 PM, Michael Haggerty wrote:
> +void ref_transaction_update(struct ref_transaction *transaction,
> + const char *refname,
> + unsigned char *new_sha1, unsigned char *old_sha1,
> + int flags, int have_old);
[s
Build out the API for dealing with a bunch of reference checks and
changes within a transaction. Define an opaque ref_transaction type
that is managed entirely within refs.c. Introduce functions for
beginning a transaction, adding updates to a transaction, and
committing/rolling back a transactio
5 matches
Mail list logo