From: David <wizzardx@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: User's mailing list? And multiple cherry pick
Date: Wed, 4 Jun 2008 10:30:08 +0200 [thread overview]
Message-ID: <18c1e6480806040130k3851a89an3fcf986feb661226@mail.gmail.com> (raw)
In-Reply-To: <m3mym1zkus.fsf@localhost.localdomain>
On Wed, Jun 4, 2008 at 10:05 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> David <wizzardx@gmail.com> writes:
>
> [Please don't remove quote attributions]
>
Thanks for the netiquette tip, I didn't know this was a bad thing. Are
<snip>s also a good thing, or is it ok to just cut out the parts that
don't need re-quoting?
>
> # make temporary branch to not move to-be-copied during rebase
> $ git checkout -b tmp-rebase to-be-copied
> # copy commits; results are in just created temporary branch
> $ git rebase --onto branch copy-from tmp-rebase
> # check if everything is all right and rename temporary branch
> # to final name
> $ git branch -M tmp-rebase branch
>
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.
David.
next prev parent reply other threads:[~2008-06-04 8:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 6:55 User's mailing list? And multiple cherry pick David
2008-06-04 6:58 ` Junio C Hamano
2008-06-04 7:13 ` David
2008-06-04 8:05 ` Jakub Narebski
2008-06-04 8:23 ` Johan Herland
2008-06-04 8:30 ` David [this message]
2008-06-04 9:39 ` Wincent Colaiuta
2008-06-04 10:02 ` David
2008-06-04 11:02 ` Wincent Colaiuta
2008-06-04 11:09 ` Jakub Narebski
2008-06-04 18:09 ` Björn Steinbrink
2008-06-04 8:16 ` Johan Herland
2008-06-04 7:39 ` Jakub Narebski
2008-06-04 8:11 ` David
2008-06-04 8:50 ` Jakub Narebski
2008-06-04 9:37 ` David
2008-06-04 9:47 ` Jakub Narebski
2008-06-04 11:36 ` Theodore Tso
2008-06-04 10:38 ` Karl Hasselström
2008-06-04 11:10 ` Miklos Vajna
2008-06-04 8:00 ` Stephan Beyer
2008-06-04 8:20 ` David
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=18c1e6480806040130k3851a89an3fcf986feb661226@mail.gmail.com \
--to=wizzardx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).