git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "git mailing list" <git@vger.kernel.org>
Subject: Re: How to split a patch
Date: Mon, 28 Jan 2008 10:32:54 +0100	[thread overview]
Message-ID: <4d8e3fd30801280132k59676921h272addab6cac6899@mail.gmail.com> (raw)
In-Reply-To: <7vhcgyuwsx.fsf@gitster.siamese.dyndns.org>

On Jan 28, 2008 10:25 AM, Junio C Hamano <gitster@pobox.com> wrote:
> "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com> writes:
>
> > I know ho to do the opposite process, rebase -i and squash is something
> > I'm really used to do but this time that trick is not going to help me.
> >
> > What is the preferred way to split a big patch in a series of
> > smaller patches?
>
>
> I personally found the procedure described there a bit on the
> sketchy side, but does "SPLITTING COMMITS" section of git-rebase
> manual help?

Yes it helps but I still wonder whether thereis a "simpler" way to achive that.
Is it possible to split a patch selecting the hunk in git gui or any
other graphical
tool?

That would be a good starting point for a newbie (like me).

Thanks!

Ciao,
-- 
Paolo
http://paolo.ciarrocchi.googlepages.com/

  reply	other threads:[~2008-01-28  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  9:05 How to split a patch Paolo Ciarrocchi
2008-01-28  9:25 ` Junio C Hamano
2008-01-28  9:32   ` Paolo Ciarrocchi [this message]
2008-01-28  9:47     ` Matthieu Moy
2008-01-28 10:27       ` Junio C Hamano
2008-01-28 10:40         ` Junio C Hamano
2008-01-28 10:49           ` Mike Hommey
2008-01-28 10:44         ` Wincent Colaiuta
2008-01-28 12:47         ` Johannes Schindelin
2008-01-28 10:27       ` Wincent Colaiuta
2008-01-28 10:37     ` Boaz Harrosh

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=4d8e3fd30801280132k59676921h272addab6cac6899@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --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 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).