Junio C Hamano wrote:
> * rr/rebase-autostash (2013-05-12) 7 commits
> - rebase: implement --[no-]autostash and rebase.autostash
> - rebase --merge: return control to caller, for housekeeping
> - rebase -i: return control to caller, for housekeeping
> - am: return control to caller, for housekeeping
> - rebase: prepare to do generic housekeeping
> - rebase -i: don't error out if $state_dir already exists
> - am: tighten a conditional that checks for $dotest
>
> This is from v3, but after a "Fixed" message in $gmane/224111 we
> haven't seen a reroll yet. Also there was an attempt for a
> follow-up, but it was never completed.
I've sent a tiny fixup for the last part. Let me know if you're
expecting something else.
> * rr/die-on-missing-upstream (2013-05-22) 2 commits
> - sha1_name: fix error message for @{<N>}, @{<date>}
> - sha1_name: fix error message for @{u}
>
> When a reflog notation is used for implicit "current branch", we
> did not say which branch and worse said "branch ''".
>
> Waiting for series of rerolls to settle.
I'm happy with the version in pu, and I don't intend to send any
re-rolls. Is there something you're not happy with?
Quick update from my side:
* publish-rev: the @{push} thing is still in the early poc stages.
* for-each-ref-pretty: not ready; working with Duy.
* push-current-head: ready but for the commit message: in your
opinion, it doesn't "fix" anything other than the output. I'll
rewrite and submit soon.
* pickaxe-doc: you had some more comments in latest iteration, but the
returns from a re-roll are diminishing. Frankly, the work is too
boring: the first few iterations were interesting, because I was
learning; now, it's mostly differences in taste. Nevertheless, I'll
re-roll when I want to sleep next.
That's about it, I think. I've abandoned everything else.
--
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