Re: What's cooking in git.git (topics)

From: Jakub Narebski <jnareb@gmail.com>
Date: Nov 1, 2007, 11:02 UTC
Message-ID: <fgcbjr$3pc$1@ger.gmane.org>
In-Reply-To: <7vmytycykt.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:

Show 8 quoted lines

> * jc/stash-create (Mon Jul 9 00:51:23 2007 -0700) 2 commits
>  + rebase: allow starting from a dirty tree.
>  + stash: implement "stash create"
> 
> Will revert at least the latter one, but perhaps both, from
> 'next'.  The traditional behaviour of refusing to work in a
> dirty tree is much safer, as the tool cannot decide where to
> unstash for you.

One of frequently requested features is ability to rebase and merge in a dirty tree (CVS-like). Perhaps we should advocate git-stash better, e.g. in error message for git-rebase / git-merge / git-pull when in dirty state.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.