From: Michael Witten <mfwitten@gmail.com>
To: git@vger.kernel.org
Subject: Re: Questions about branches in git
Date: Thu, 28 Jan 2010 12:35:59 -0800 (PST) [thread overview]
Message-ID: <4b61f52f.1d255e0a.4cc1.7f37@mx.google.com> (raw)
In-Reply-To: <b4087cc51001281203q1f467480sdf848c9d3ced323b@mail.gmail.com>
On Thu, Jan 28, 2010 at 2:03 PM, Michael Witten <mfwitten@gmail.com> wrote:
> These übercommits would also allow developers to make a string of
> commits that by themselves break things but together formulate a
> complete solution; because the übercommits encapsulate the breakage,
> bisection would still be simple (no fear of dealing with broken
> commits), but the small manageable commits would still be available
As a corollary to this, developers can maintain patch integrity.
Quite often, I've sent a patch off to some project only to have
the maintainer `tweak' the result before making a commit. However,
I frankly don't want my name attached to someone else's work,
because I may disagree with what has been done.
Were übercommits available, the maintainer could commit my original
work and then make a new `tweak' commit and then bundle the 2 together
as an übercommit in order to encapsulate this series of events.
next prev parent reply other threads:[~2010-01-28 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 18:44 Questions about branches in git Mike Linck
2010-01-28 20:03 ` Michael Witten
2010-01-28 20:20 ` Michael Witten
2010-01-28 20:35 ` Michael Witten [this message]
2010-01-28 21:17 ` Mike Linck
2010-01-28 21:29 ` Jens Lehmann
2010-01-28 21:38 ` Mike Linck
2010-01-28 23:07 ` Heiko Voigt
2010-01-29 0:03 ` Nanako Shiraishi
2010-01-29 3:03 ` Junio C Hamano
2010-01-28 22:04 ` Nicolas Pitre
2010-01-28 22:13 ` Eugene Sajine
2010-01-28 22:14 ` David Aguilar
2010-01-28 22:18 ` Michael Witten
2010-01-28 22:56 ` Mike Linck
2010-01-28 23:01 ` Michael Witten
2010-01-29 10:07 ` Peter Krefting
2010-01-28 23:00 ` Martin Langhoff
2010-01-28 23:33 ` Junio C Hamano
2010-01-29 1:16 ` Mike Linck
2010-01-29 10:06 ` Peter Krefting
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=4b61f52f.1d255e0a.4cc1.7f37@mx.google.com \
--to=mfwitten@gmail.com \
--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.