git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-merge --squash

From
TGThomas Glanzmann <sithglan@stud.uni-erlangen.de>
Date
Jun 23, 2006, 12:25 UTC
Message-ID
<20060623122501.GD15631@cip.informatik.uni-erlangen.de>
In-Reply-To
<7vd5d09pe2.fsf@assigned-by-dhcp.cox.net>
Hello Junio,
Show 5 quoted lines
> So in that sense I would imagine --squash is not really useless
> in such a situation as I made it sound like, but at the same
> time I suspect people might be better off to use tools like
> StGIT which are specially designed to support such a workflow if
> they were to do this.

thanks for --squash. So --squash is basically a 'suck multiple deltas from another branch into ., but don't commit it'. I very often use that way of work flow. I do small and many commits, and when I am done I merge them to one a bit bigger one and submit it upstream. I useally use 'one branch per feature'.

        Thomas
Previous: Junio C HamanoNext: Johannes Schindelin
Message 3 of 6 in “git-merge --squash”
  1. git-merge --squashJunio C Hamano, Jun 23, 2006
  2. Junio C HamanoJun 23, 2006
  3. Thomas GlanzmannJun 23, 2006
  4. Johannes SchindelinJun 23, 2006
  5. Thomas GlanzmannJun 23, 2006
  6. Junio C HamanoJun 23, 2006

Read the whole thread, see it on lore, or plain text.

$ 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.