Re: [PATCH 0/20] rs/ref-transaction-1 (Re: Transaction patch series overview)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 27, 2014, 22:37 UTC
- Message-ID
- <xmqqwq9tbltl.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <xmqq1ts1d3jx.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 22 quoted lines
> Jonathan Nieder <jrnieder@gmail.com> writes: > >> Jonathan Nieder wrote: >> >>> This series teaches the tag, replace, commit, cherry-pick, >>> fast-import, checkout -b, branch, receive-pack, and http-fetch >>> commands and all update_ref and delete_ref callers to use the ref >>> transaction API instead of lock_ref_sha1. >>> >>> The main user-visible change should be some cosmetic changes to error >>> messages. The series also combines multiple ref updates into a single >>> transaction in 'git http-fetch -w' and when writing tags in >>> fast-import but otherwise doesn't change the granularity of >>> transactions. >>> >>> Reviewed at https://code-review.googlesource.com/#/q/topic:ref-transaction-1 > > Thanks. > > Will queue, but the some other topics may have to disappear from my > tree while I try to rebase them on top (or while I wait for you guys > to send a reroll, making it unnecesary to do the rebase myself).
I managed to rebase all the rs/ref-transaction* topics and pushed out the result in 'pu'. Please eyeball the result.
I had to bump nd/multiple-work-trees, which Duy asked to kick out of 'next' earlier, out of 'pu' because I did not want to deal with conflict resolution that will go to waste when the topic is rerolled which would happen soon.