All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: git@vger.kernel.org
Subject: Test that every revision builds before pushing changes?
Date: Thu, 26 Mar 2009 17:29:58 +1100	[thread overview]
Message-ID: <87myb8aja1.fsf@rimspace.net> (raw)

G'day.

I would like to ensure that my commits are fully bisectable before I
commit them to an upstream repository, at least to the limits of an
automatic tool for testing them.

'git bisect run' is similar: it can automatically locate the breaking in
a test suite, for example, but that doesn't help me in the case of three
commits, A (good), B (bad) and C (good, fixing B).

I would much rather, in this case, use rebase to fix B so that it, too,
builds before I push the changes and pollute a public repository with a
broken changeset — and make bisect that much harder to use in future.

Regards,
        Daniel

             reply	other threads:[~2009-03-26  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  6:29 Daniel Pittman [this message]
2009-03-26  8:16 ` Test that every revision builds before pushing changes? Andreas Ericsson
2009-03-26  9:10   ` Daniel Pittman
2009-03-26  9:46     ` Andreas Ericsson
2009-03-27  1:30       ` Daniel Pittman
2009-03-26  9:49     ` Jeff King
2009-03-26  9:59       ` Wincent Colaiuta

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=87myb8aja1.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --cc=git@vger.kernel.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.