From: Jan Hudec <bulb@ucw.cz>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Opinions on bug fix organisation
Date: Fri, 18 May 2007 21:50:00 +0200 [thread overview]
Message-ID: <20070518195000.GC3327@efreet.light.src> (raw)
In-Reply-To: <200705161138.30134.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On Wed, May 16, 2007 at 11:38:28 +0100, Andy Parkins wrote:
> Now, I want to make a commit that fixes that bug. These are the options:
>
> * -- * -- B -- * -- * -- * -- F
>
> or
>
> * -- * -- B -- * -- * -- * -- M
> \ /
> --------------- F
>
> That is - just commit a fix or, commit the fix, "F", directly on "B" then
> merge that fix back to HEAD with "M".
>
> I quite like option 2 because it records intent - i.e. "I wish I could have
> gone back and changed this revision, but I can't", but it makes a more
> complicated history.
>
> What do people think?
The big advantage of the later is, that if you have:
* -- B -- * -- * -- M1
\
-- * -- * -- M2
You can merge the fix done on yet another branch into how many branches you
need, so:
* -- B -- * -- * ----- M1
\ /
-- * -- * ----/- M2
\ / /
----------F---
If you had the fix on one of the branches, you could only cherry-pick it to
the other, but the history would not really reflect that.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-18 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 10:38 Opinions on bug fix organisation Andy Parkins
2007-05-16 14:46 ` Brian Gernhardt
2007-05-16 17:55 ` Junio C Hamano
2007-05-16 21:20 ` Andy Parkins
2007-05-16 21:38 ` Shawn O. Pearce
2007-05-18 8:11 ` Johannes Sixt
2007-05-16 21:51 ` Martin Langhoff
2007-05-18 19:50 ` Jan Hudec [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=20070518195000.GC3327@efreet.light.src \
--to=bulb@ucw.cz \
--cc=andyparkins@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 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).