Michael Haggerty mhag...@alum.mit.edu writes:
I assumed that rolling back a non-consummated transaction in the case of
early program death should be the responsibility of the library, not of
the caller. If I'm correct, the caller(s) won't have to be modified
when the atexit facility is
On 04/03/2014 05:57 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
I assumed that rolling back a non-consummated transaction in the case of
early program death should be the responsibility of the library, not of
the caller. If I'm correct, the caller(s) won't have
Michael Haggerty mhag...@alum.mit.edu writes:
This change is mostly clerical: the parse_cmd_*() functions need to
use local variables rather than a struct ref_update to collect the
arguments needed for each update, and then call ref_transaction_*() to
queue the change rather than building up
On 04/01/2014 09:46 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
This change is mostly clerical: the parse_cmd_*() functions need to
use local variables rather than a struct ref_update to collect the
arguments needed for each update, and then call
4 matches
Mail list logo
