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

Re: User's mailing list? And multiple cherry pick

From
Wincent Colaiuta <win@wincent.com>
Date
Jun 4, 2008, 09:39 UTC
Message-ID
<D11EAC1A-B59E-4857-A31F-809809310E40@wincent.com>
In-Reply-To
<18c1e6480806040130k3851a89an3fcf986feb661226@mail.gmail.com>
El 4/6/2008, a las 10:30, David escribió:
Show 18 quoted lines
> Thanks :-) This still isn't what I had in mind (see my earlier post
> with examples), but I realise now, thanks to your post, that I can
> probably do it like this:
>
> 1) Make a temporary branch off the topic
>
> 2) Rebase the temporary branch onto master interactively (maybe or
> maybe not with --onto), and in interactive mode take out, reorder,
> etc.
>
> 3) Check & test the temporary branch
>
> 4) Merge the temporary branch into master, and drop the temporary  
> branch.
>
> 5) Rebase the original topic branch onto the new master.
>
> Thanks to all the posters for their tips.

Sounds like it would definitely work but it also sounds like a lot of repetitive "busy work"[1] which could be avoided by using finer- grained topic branches in the first place.

In the basic case Git makes it incredibly easy to split off topic branches and merge them back in, and when you do this you're working in synergy with the tool. But while what you're wanting to do is certainly possible you can also see that it has a lot of fiddly, error- prone overhead in which you're juggling temporary branches and commits back and forth in a complicated way. Not working in synergy with the tool.

I know that I'd soon get tied of this "busy work" if I had to do it; maybe with time you'll be able to transition to a style in which you make more, smaller topic branches, which can really be treated as logically-grouped topics and merged in as a whole rather than sifted out into separate sub-topics.

Having said that, the ability to pass multiple commits or ranges of commits to "git cherry-pick" is a logical enough enhancement, if someone is interested enough in this feature to actually do the work.

Wincent
[1] http://en.wikipedia.org/wiki/Busy_work
Previous: DavidNext: David
Message 7 of 22 in “User's mailing list? And multiple cherry pick”
  1. DavidJun 4, 2008
  2. Junio C HamanoJun 4, 2008
  3. DavidJun 4, 2008
  4. Jakub NarebskiJun 4, 2008
  5. Johan HerlandJun 4, 2008
  6. DavidJun 4, 2008
  7. Wincent ColaiutaJun 4, 2008
  8. DavidJun 4, 2008
  9. Wincent ColaiutaJun 4, 2008
  10. Jakub NarebskiJun 4, 2008
  11. Björn SteinbrinkJun 4, 2008
  12. Johan HerlandJun 4, 2008
  13. Jakub NarebskiJun 4, 2008
  14. DavidJun 4, 2008
  15. Jakub NarebskiJun 4, 2008
  16. DavidJun 4, 2008
  17. Jakub NarebskiJun 4, 2008
  18. Theodore TsoJun 4, 2008
  19. Karl HasselströmJun 4, 2008
  20. Miklos VajnaJun 4, 2008
  21. Stephan BeyerJun 4, 2008
  22. DavidJun 4, 2008

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.