All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Christian Couder <chriscool@tuxfamily.org>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [GSoC update] Sequencer: Debating the UI
Date: Tue, 14 Jun 2011 00:31:43 -0500	[thread overview]
Message-ID: <20110614053143.GA24882@elie> (raw)
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

  reply	other threads:[~2011-06-14  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 15:23 [GSoC update] Sequencer: Debating the UI Ramkumar Ramachandra
2011-06-14  5:31 ` Jonathan Nieder [this message]
2011-06-14  6:00   ` Ramkumar Ramachandra
2011-06-14 11:45     ` Christian Couder
2011-06-20 15:51     ` Ramkumar Ramachandra
2011-06-21  6:21       ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110614053143.GA24882@elie \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.