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 (Mar 2019, #01; Wed, 6)
Date: Wed, 6 Mar 2019 14:41:46 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1903061441200.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqa7i8ss4l.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 6 Mar 2019, Junio C Hamano wrote:
> * ps/stash-in-c (2019-03-01) 28 commits
> - 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: add test for --intent-to-add file
> - 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'.
Yes, yes, yes!
Thank you so much!
Dscho
next prev parent reply other threads:[~2019-03-06 13:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:34 What's cooking in git.git (Mar 2019, #01; Wed, 6) Junio C Hamano
2019-03-06 1:41 ` Denton Liu
2019-03-06 23:43 ` Junio C Hamano
2019-03-06 4:43 ` Jeff King
2019-03-06 23:45 ` Junio C Hamano
2019-03-06 9:44 ` Duy Nguyen
2019-03-06 23:46 ` Junio C Hamano
2019-03-07 12:34 ` Philip Oakley
2019-03-07 12:54 ` Duy Nguyen
2019-03-09 17:27 ` Thomas Gummerer
2019-03-09 18:04 ` Elijah Newren
2019-03-10 18:27 ` Thomas Gummerer
2019-03-12 23:30 ` [PATCH v2] glossary: add definition for overlay Thomas Gummerer
2019-03-13 1:13 ` Duy Nguyen
2019-03-15 22:31 ` Thomas Gummerer
2019-03-13 1:42 ` Junio C Hamano
2019-03-15 23:10 ` Thomas Gummerer
2019-03-17 20:19 ` [PATCH v3] " Thomas Gummerer
2019-03-21 14:48 ` Philip Oakley
2019-03-22 4:54 ` Junio C Hamano
2019-03-28 21:05 ` Thomas Gummerer
2019-03-08 0:02 ` What's cooking in git.git (Mar 2019, #01; Wed, 6) Junio C Hamano
2019-03-06 12:39 ` Johannes Schindelin
2019-03-18 7:08 ` Junio C Hamano
2019-03-06 12:47 ` Johannes Schindelin
2019-03-06 23:55 ` Junio C Hamano
2019-03-06 13:26 ` Johannes Schindelin
2019-03-06 13:41 ` Johannes Schindelin [this message]
2019-03-06 23:56 ` ps/stash-in-c, was " Junio C Hamano
2019-03-06 18:10 ` Jonathan Tan
2019-03-07 0:19 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* 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.1903061441200.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).