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

Re: [GSoC update] Sequencer: Debating the UI

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jun 14, 2011, 05:31 UTC
Message-ID
<20110614053143.GA24882@elie>
In-Reply-To
<BANLkTinxx5qFuhwsUt3JeXOO7TjBj8wFvw@mail.gmail.com>
Ramkumar Ramachandra wrote:
> I might like
> to send a quick series based on my earlier series for inclusion, but I
> can't figure out a good subset:

I would love to use a working "cherry-pick --continue". :) I would use it like this:

	$ : grumble, grumble, source package format that requires a
	$ : tarball followed by a linear sequence of patches
	$ git checkout -b release+patches v1.0
	$ git cherry-pick --no-merges -x -s HEAD..origin/master
	... ticks away for a while, then presents a conflict
	$ git diff; fix fix fix; git add -u; make test; git commit -v
	$ git cherry-pick --continue
	...
	$ git diff origin/master; # matches up?  good.
	$ git format-patch -k --patience -o patches v1.0..HEAD

Speaking of which, do you have a git tree that testers should use / send patches against? E.g., is the "sequencer" branch at git://github.com/artagnon/git.git the one to play with?

Thanks; exciting times.

Regards, Jonathan

Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 2 of 6 in “[GSoC update] Sequencer: Debating the UI”
  1. Ramkumar RamachandraJun 13, 2011
  2. Jonathan NiederJun 14, 2011
  3. Ramkumar RamachandraJun 14, 2011
  4. Christian CouderJun 14, 2011
  5. Ramkumar RamachandraJun 20, 2011
  6. Christian CouderJun 21, 2011

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.