All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Carl Worth <cworth@cworth.org>
Subject: Re: [PATCH] Documentation: Transplanting branch with git-rebase --onto
Date: Mon, 06 Nov 2006 14:53:29 -0800	[thread overview]
Message-ID: <7v4ptcchli.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200611061912.46436.jnareb@gmail.com> (Jakub Narebski's message of "Mon, 6 Nov 2006 19:12:45 +0100")

Jakub Narebski <jnareb@gmail.com> writes:

> Added example of transplantig feature branch from one development
> branch (for example "next") into the other development branch (for
> example "master").
>
> [jn: with a little help from Junio]
>
> Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> ---
> What about this?

I agree with Carl that the original example of --onto was not
clear why it is a good thing, so I am inclined to follow his
suggestion and drop the original example and keep your second
one yanked from your try#1 patch when committing, if it is Ok
with you.



  reply	other threads:[~2006-11-06 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04 21:05 [PATCH/RFC] Documentation: Two more git-rebase --onto examples Jakub Narebski
2006-11-05  1:08 ` Junio C Hamano
2006-11-05 10:22   ` Jakub Narebski
2006-11-06 18:12     ` [PATCH] Documentation: Transplanting branch with git-rebase --onto Jakub Narebski
2006-11-06 22:53       ` Junio C Hamano [this message]
2006-11-06 23:14         ` Jakub Narebski
2006-11-06 18:14     ` [PATCH/RFC] Documentation: Two more git-rebase --onto examples Carl Worth
2006-11-06 19:18       ` Junio C Hamano

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=7v4ptcchli.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=cworth@cworth.org \
    --cc=git@vger.kernel.org \
    --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 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.