From: ali@internetdog.org (Ali Bahar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: git format-patch: skipping interim commits.
Date: Sun, 24 Jul 2011 14:20:09 +0800 [thread overview]
Message-ID: <20110724062009.GA1889@internetdog.org> (raw)
In-Reply-To: <CAE0An6cHsJaGMJqT5dnxB_b2xnAe9SZ6p-Fjw6XHeAnWd+M18A@mail.gmail.com>
On Sat, Jul 23, 2011 at 10:42:44PM -0700, Manish Katiyar wrote:
> On Sat, Jul 23, 2011 at 9:52 PM, Ali Bahar <ali@internetdog.org> wrote:
> > When I run 'git format-patch' to prepare a submission, it creates a
> > patch-file for every commit. While this is sometimes fine, it often
> > isn't: I want it to skip all the interim commits which I did during
> > development. There is no point in (and likely prosecutable in several
> > everyone else tackles this. I expect that it is more a _workflow_
> > issue than having to do with specifying revision ranges on the
> > command-line.
>
> Hi,
>
> Looks like you want to generate a single commit from multiple commits.
Yup. Well phrased.
> Have a look at "git rebase --interactive". You will
Hmm, that's not what I thought rebase was for! I knew of its
branch-synch functionality, not this. Then again, the man page for
git-rebase qualifies for the Stroustrup Award for Clarity! (Either
that, or a steganography award!) ;-)
Thanks much.
> be able to merge multiple commits into a single commit. So the
> workflow would be something like
>
> a) Create a new test branch
> b) git rebase --interactive commit-id
I take back what I said about the man page; 66% into it, after the
memorable first page, in the INTERACTIVE MODE section, it explains
perfectly.
> c) Merge commits,
It seems to call these "squash", instead of "merge". No wonder grep
didn't work!
> d) git format-patch ....
Thanks much. Greatly appreciated.
thanks,
ali
prev parent reply other threads:[~2011-07-24 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 4:52 git format-patch: skipping interim commits Ali Bahar
2011-07-24 5:42 ` Manish Katiyar
2011-07-24 6:20 ` Ali Bahar [this message]
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=20110724062009.GA1889@internetdog.org \
--to=ali@internetdog.org \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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.