All of lore.kernel.org
 help / color / mirror / Atom feed
From: ali@internetdog.org (Ali Bahar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: git format-patch: skipping interim commits.
Date: Sun, 24 Jul 2011 12:52:41 +0800	[thread overview]
Message-ID: <20110724045241.GA1918@internetdog.org> (raw)

Hi all,

(yes, I _am_ aware that there is a separate git mailing list. This
seemed to be more apt for _here_, as a first attempt.)

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
jurisdictions) submitting the interim miscellany, thereby creating
needless, non-Acked, log entries in master.

I do have a crude work-around for this, but I prefer to find out how
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.


thanks,
ali
PS the crude work-around is to copy all the changes into a clean
branch, and do a single commit. But that's error-prone when you have
numerous files, and several sets of commits.

PPS A simplified example, given a Master and a Dev branch:
1. Dev has lots of interim commits, for a single, logically-cohesive
  change. Once the work is complete, I want to create a single patch
  file for the entire delta against Master.
2. Dev will next have another set of commits. These are logically
  related and, once done, are to result in another single patch file.
3. and so on.

This is all subject to Release Early, Release Often, so I am not
talking about sitting on a bunch of changes for too long!

             reply	other threads:[~2011-07-24  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24  4:52 Ali Bahar [this message]
2011-07-24  5:42 ` git format-patch: skipping interim commits Manish Katiyar
2011-07-24  6:20   ` Ali Bahar

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=20110724045241.GA1918@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.