Re: What's cooking in git.git (Jul 2015, #05; Mon, 20)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> * dt/refs-backend-preamble (2015-07-13) 7 commits
>  - git-stash: use update-ref --create-reflog instead of creating files
>  - update-ref and tag: add --create-reflog arg
>  - refs: add REF_FORCE_CREATE_REFLOG flag
>  - git-reflog: add exists command
>  - refs: new public ref function: safe_create_reflog
>  - refs: Break out check for reflog autocreation
>  - refs.c: add err arguments to reflog functions
> 
>  In preparation for allowing different "backends" to store the refs
>  in a way different from the traditional "one ref per file in $GIT_DIR
>  or in a $GIT_DIR/packed-refs file" filesystem storage, reduce
>  direct filesystem access to ref-like things like CHERRY_PICK_HEAD
>  from scripts and programs.
> 
>  Still under discussion.
> 
>  Will hold.

What's left to discuss on this one? I think the latest version addresses
all concerns, but I'm happy to do another reroll or discuss further if
necessary.


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]