Re: [GSoC update] Sequencer: Debating the UI

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]