All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ps/stash-in-c, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)
Date: Tue, 29 Jan 2019 15:23:34 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1901291523060.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqq4l9s9zee.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 28 Jan 2019, Junio C Hamano wrote:

> * ps/stash-in-c (2019-01-18) 28 commits
>  - stash: fix segmentation fault when files were added with intent
>  - tests: add a special setup where stash.useBuiltin is off
>  - stash: optionally use the scripted version again
>  - stash: add back the original, scripted `git stash`
>  - stash: convert `stash--helper.c` into `stash.c`
>  - stash: replace all `write-tree` child processes with API calls
>  - stash: optimize `get_untracked_files()` and `check_changes()`
>  - stash: convert save to builtin
>  - stash: make push -q quiet
>  - stash: convert push to builtin
>  - stash: convert create to builtin
>  - stash: convert store to builtin
>  - stash: convert show to builtin
>  - stash: convert list to builtin
>  - stash: convert pop to builtin
>  - stash: convert branch to builtin
>  - stash: convert drop and clear to builtin
>  - stash: convert apply to builtin
>  - stash: mention options in `show` synopsis
>  - stash: add tests for `git stash show` config
>  - stash: rename test cases to be more descriptive
>  - t3903: modernize style
>  - stash: improve option parsing test coverage
>  - ident: add the ability to provide a "fallback identity"
>  - strbuf.c: add `strbuf_insertf()` and `strbuf_vinsertf()`
>  - strbuf.c: add `strbuf_join_argv()`
>  - sha1-name.c: add `get_oidf()` which acts like `get_oid()`
>  - Merge branch 'sd/stash-wo-user-name'
> 
>  "git stash" rewritten in C.
> 
>  Will merge to 'next'.

Yesssss! Thank you so much!

Ciao,
Dscho

  parent reply	other threads:[~2019-01-29 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 22:43 What's cooking in git.git (Jan 2019, #04; Mon, 28) Junio C Hamano
2019-01-29  7:22 ` Torsten Bögershausen
2019-01-29 12:54 ` pw/rebase-x-sanity-check, was " Johannes Schindelin
2019-01-29 18:11   ` Junio C Hamano
2019-01-29 14:03 ` js/rebase-am, " Johannes Schindelin
2019-01-29 14:06 ` tt/bisect-in-c, " Johannes Schindelin
2019-01-29 15:39   ` Johannes Schindelin
2019-01-29 14:15 ` en/rebase-merge-on-sequencer, " Johannes Schindelin
2019-01-29 14:21 ` Johannes Schindelin
2019-01-29 14:23 ` Johannes Schindelin [this message]
2019-01-29 14:26 ` [PATCH] Fix typos in whats-cooking.txt, was " Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.1901291523060.41@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.