Hi Dscho,
On Thu, Jan 3, 2019 at 5:27 AM Johannes Schindelin
wrote:
>
> Hi Elijah,
>
...
> > I was going to re-ping in early January. Anyway, it may be worth at
> > least updating your note to "reroll exists".
>
> It is early January! ;-)
Indeed...ping incoming. :-)
>
> Ciao,
> Dscho
Hi Elijah,
On Fri, 28 Dec 2018, Elijah Newren wrote:
> On Fri, Dec 28, 2018 at 10:04 AM Junio C Hamano wrote:
>
> > * en/rebase-merge-on-sequencer (2018-11-08) 2 commits
> > - rebase: implement --merge via git-rebase--interactive
> > - git-rebase, sequencer: extend --quiet option for the inte
Hi Junio,
On Fri, 28 Dec 2018, Junio C Hamano wrote:
> * ps/stash-in-c (2018-11-26) 22 commits
> . stash: replace all `write-tree` child processes with API calls
> . stash: optimize `get_untracked_files()` and `check_changes()`
> . stash: convert `stash--helper.c` into `stash.c`
> . stash: co
On Fri, Dec 28, 2018 at 10:04:13AM -0800, Junio C Hamano wrote:
> * dl/remote-save-to-push (2018-12-11) 1 commit
> - remote: add --save-to-push option to git remote set-url
>
> "git remote set-url" learned a new option that moves existing value
> of the URL field to pushURL field of the remote
Alban Gruin writes:
>> With too many topics in-flight that touch sequencer and rebaser,
>> this need to wait giving precedence to other topics that fix bugs.
>>
>
> Most of these topics have reached master and have been released in git
> 2.20. Currently, there is four topics actually touching
Hi Junio,
Le 28/12/2018 à 19:04, Junio C Hamano a écrit :
> * ag/sequencer-reduce-rewriting-todo (2018-11-12) 16 commits
> . rebase--interactive: move transform_todo_file() to rebase--interactive.c
> . sequencer: fix a call to error() in transform_todo_file()
> . sequencer: use edit_todo_list()
On Fri, Dec 28, 2018 at 10:04 AM Junio C Hamano wrote:
> Sorry for being slow to recover from the year-end slowness; the 2.20
> release being rather large-ish and needed brown-paper-bag fixes soon
> after it, my temporary trans-pacific migration, or me catching cold
> that I haven't shaken off, di
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The current state is that 'next' h
8 matches
Mail list logo
