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

Re: branch vs. cherry-pick workflow

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Jul 8, 2009, 22:59 UTC
Message-ID
<slrnh5a96q.95d.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<24399128.post@talk.nabble.com>
On 2009-07-08 20:51:38, jshalvi <jshalvi@gmail.com> wrote:
> It seems dangerous to rely on cherry-picking like this.  Are there any good
> technical reasons to insist on a branch/merge workflow as opposed to this
> commit/cherry-pick workflow?  It may sound like a simple question, but

man git-workflows and look at the section "MANAGING BRANCHES" gives a very nice, though brief, overview of why branching is better in general.

Regards,
Sitaram
Previous: jshalvi
Message 2 of 2 in “branch vs. cherry-pick workflow”
  1. jshalviJul 8, 2009
  2. Sitaram ChamartyJul 8, 2009

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.