From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/5] Write a good 'git stash store' for autostash
Date: Fri, 14 Jun 2013 16:01:59 +0530 [thread overview]
Message-ID: <1371205924-8982-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
So, I've taken Junio's suggestion and designed a proper command-line
interface for 'git stash store' in this iteration:
git stash store [-m <message>] [-e <error>] <commit>
The error string will be passed through eval_gettext before it is
printed. Otherwise, the idea is the same: to clean up the logic
surrounding autostash.
Thanks.
Ramkumar Ramachandra (5):
stash doc: add a warning about using create
stash doc: document short form -p in synopsis
stash: simplify option parser for create
stash: introduce 'git stash store'
rebase: use 'git stash store' to simplify logic
Documentation/git-stash.txt | 12 ++++++++--
git-rebase.sh | 6 +----
git-stash.sh | 53 ++++++++++++++++++++++++++++++++++++---------
t/t3903-stash.sh | 19 ++++++++++++++++
4 files changed, 73 insertions(+), 17 deletions(-)
--
1.8.3.1.383.g0d5ad6b
next reply other threads:[~2013-06-14 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 10:31 Ramkumar Ramachandra [this message]
2013-06-14 10:32 ` [PATCH 1/5] stash doc: add a warning about using create Ramkumar Ramachandra
2013-06-14 12:27 ` Phil Hord
2013-06-14 15:11 ` Junio C Hamano
2013-06-14 10:32 ` [PATCH 2/5] stash doc: document short form -p in synopsis Ramkumar Ramachandra
2013-06-14 10:32 ` [PATCH 3/5] stash: simplify option parser for create Ramkumar Ramachandra
2013-06-14 10:32 ` [PATCH 4/5] stash: introduce 'git stash store' Ramkumar Ramachandra
2013-06-14 12:39 ` Phil Hord
2013-06-14 10:32 ` [PATCH 5/5] rebase: use 'git stash store' to simplify logic Ramkumar Ramachandra
2013-06-14 12:47 ` Phil Hord
2013-06-14 13:40 ` Ramkumar Ramachandra
2013-06-14 14:26 ` [PATCH v2 0/5] Write a good 'git stash store' for autostash Junio C Hamano
2013-06-14 15:16 ` Ramkumar Ramachandra
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=1371205924-8982-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--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 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 NNTP newsgroup(s).