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

Re: [RFC] Patches exchange is bad?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 16, 2005, 20:39 UTC
Message-ID
<Pine.LNX.4.63.0508162238400.19656@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20050816200132.88287.qmail@web26304.mail.ukl.yahoo.com>
Hi,
On Tue, 16 Aug 2005, Marco Costalba wrote:
Show 9 quoted lines
> Suppose a possible scenario involves using a couple of git archives, one 
> for releases and stable code, say MAIN, and one for experimental stuff  
> or new development, say HEAD.
> 
> Suppose there is stuff in HEAD you don't want merged in MAIN, more,
> you need to update MAIN with only a subset of patches in HEAD, peraphs 
> in different order. Or simply, you are not interested to see the history 
> of the HEAD tree when looking MAIN. All this points could keep you 
> from merging.

This looks like a good description of cherry picking. See StGIT (and to a certain extent, git-cherry) for that.

Ciao, Dscho

Previous: Marco CostalbaNext: Junio C Hamano
Message 2 of 5 in “[RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 16, 2005
  2. Johannes SchindelinAug 16, 2005
  3. Junio C HamanoAug 16, 2005
  4. Martin LanghoffAug 16, 2005
  5. Catalin MarinasAug 17, 2005

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.