Re: [PATCH v2] Teach stash to parse -m/--message like commit does

Phil Hord writes: > `git stash push -m foo` uses "foo" as the message for the stash. But > `git stash push -m"foo"` does not parse successfully. Similarly > `git stash push --message="My stash message"` also fails. The stash > documentation doesn't suggest this syntax

Re: [PATCH v2] Teach stash to parse -m/--message like commit does

On Wed, Nov 22, 2017 at 01:20:30PM -0800, Phil Hord wrote: > `git stash push -m foo` uses "foo" as the message for the stash. But > `git stash push -m"foo"` does not parse successfully. Similarly > `git stash push --message="My stash message"` also fails. The stash > documentation doesn't

[PATCH v2] Teach stash to parse -m/--message like commit does

`git stash push -m foo` uses "foo" as the message for the stash. But `git stash push -m"foo"` does not parse successfully. Similarly `git stash push --message="My stash message"` also fails. The stash documentation doesn't suggest this syntax should work, but gitcli does and my fingers have

Re: [PATCH] stash: Learn to parse -m/--message like commit does

Phil Hord writes: > `git stash push -m foo` uses "foo" as the message for the stash. But > `git stash push -m"foo"` does not parse successfully. Similarly > `git stash push --message="My stash message"` also fails. Nothing > in the documentation suggests this syntax should

[PATCH] stash: Learn to parse -m/--message like commit does

`git stash push -m foo` uses "foo" as the message for the stash. But `git stash push -m"foo"` does not parse successfully. Similarly `git stash push --message="My stash message"` also fails. Nothing in the documentation suggests this syntax should work, but it does work for `git commit`, and my

Re: stash: learn to parse -m/--message like commit does

Hi, Phil Hord wrote: > `git stash push -m foo` uses "foo" as the message for the stash. But > `git stash push -m"foo"` does not parse successfully. Similarly > `git stash push --message="My stash message"` also fails. Nothing > in the documentation suggests this syntax should work, "git help

Re: stash: learn to parse -m/--message like commit does

Hm.. Sorry about the formatting here. It's been a while. I'll try again. On Tue, Nov 21, 2017 at 3:07 PM, Phil Hord wrote: > `git stash push -m foo` uses "foo" as the message for the stash. But > `git stash push -m"foo"` does not parse successfully. Similarly > `git

stash: learn to parse -m/--message like commit does

`git stash push -m foo` uses "foo" as the message for the stash. But `git stash push -m"foo"` does not parse successfully. Similarly `git stash push --message="My stash message"` also fails. Nothing in the documentation suggests this syntax should work, but it does work for `git commit`, and my

Re: [PATCH 2/4] merge: do no-verify like commit

On Fri, Sep 22, 2017 at 5:04 AM, Michael J Gruber wrote: > f8b863598c ("builtin/merge: honor commit-msg hook for merges", 2017-09-07) > introduced the no-verify to merge for bypassing the commit-msg hook, > though in a different way from the implementation in commit.c. > > Change

[PATCH 2/4] merge: do no-verify like commit

f8b863598c ("builtin/merge: honor commit-msg hook for merges", 2017-09-07) introduced the no-verify to merge for bypassing the commit-msg hook, though in a different way from the implementation in commit.c. Change the implementation in merge.c to be the same as in merge.c so that both do the same

[PATCH 16/31] refs.c: add an error argument to create/delete/update just like commit

Update the signatures for transaction create/delete/update and add a strbuf err argument we can use to pass an error back to the caller. We will need this later once we start moving checks from _commit to _update. Change all callers that would die() on _commit failures to handle _update failures

Re: Like commit -a, but...

On Mon, 05 Nov 2012 21:29:48 +, Andreas Krey wrote: ... But still I'd like to know if there is a cleaner solution, esp. with respect to the index. Actually, it seems commit -m 'index' commit -a -m 'worktree' ...push git reset HEAD^ git reset --soft HEAD^ might do the index trick.

Like commit -a, but...

Hi all, I have a workflow for which I can't quite find the git tooling. Essentially what I want is like 'git commit -a', except that I want the resulting commit on a branch I name instead of the current one, and I want my current index not being modified. At the moment I emulate that via git

Re: Like commit -a, but...

On Mon, 05 Nov 2012 21:56:28 +0100, Andreas Krey a.k...@gmx.de wrote: On Mon, 05 Nov 2012 21:29:48 +, Andreas Krey wrote: ... But still I'd like to know if there is a cleaner solution, esp. with respect to the index. Actually, it seems commit -m 'index' commit -a -m 'worktree'

Re: Like commit -a, but...

Andreas Krey a.k...@gmx.de writes: But is there a direct way to convert the current working tree into a tree object? You can create a temporary index by setting the GIT_INDEX_FILE env var. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3