From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Wim Van Sebroeck <wim@iguana.be>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: Re: [PATCH] 2.6.0 - Watchdog patches
Date: Mon, 29 Dec 2003 15:36:15 -0500 [thread overview]
Message-ID: <3FF0903F.1030604@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312291209150.2113@home.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 29 Dec 2003, Wim Van Sebroeck wrote:
>
>>Hi Linus, Andrew,
>>
>>please do a
>>
>> bk pull http://linux-watchdog.bkbits.net/linux-2.5-watchdog
>
>
> This tree has 38 deltas, all just merges.
>
> The end result is a horribly messy revision tree, for a few one-liners.
>
> I'm going to take the patch as a patch instead, and hope that you'll throw
> your BK tree away.
>
> Please don't follow the release tree in your development trees, it makes
> it impossible to see how the revision history happened.
Agreed. Several BK developers do this, forgetting that one of things
that makes BK so useful is its merge technology.
I recommend (assuming no patches outstanding),
* clone latest tree
* do development
* only 'bk pull' from latest tree iff (a) you are about to submit to
Linus/Andrew or (b) you know there is a conflicting change in upstream
Pulling the latest, just to be up-to-date, just obfuscates things and
needlessly increases the size of the master ChangeSet file.
Jeff
next prev parent reply other threads:[~2003-12-29 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 10:51 [PATCH] 2.6.0-test4 - Watchdog patches - Documentation Wim Van Sebroeck
2003-12-29 19:52 ` [PATCH] 2.6.0 - Watchdog patches Wim Van Sebroeck
2003-12-29 20:11 ` Linus Torvalds
2003-12-29 20:22 ` Wim Van Sebroeck
2003-12-29 20:30 ` Linus Torvalds
2003-12-30 0:49 ` Matthias Andree
2003-12-30 6:36 ` Linus Torvalds
2003-12-30 13:36 ` [PATCH] 2.6.0 - Watchdog patches (BK consistency checks) Ed Tomlinson
2003-12-30 19:13 ` Andy Isaacson
2003-12-30 19:56 ` Eric D. Mudama
2003-12-30 20:16 ` Andy Isaacson
2003-12-31 16:33 ` Ed Tomlinson
2003-12-31 15:01 ` Ed Tomlinson
2003-12-31 17:42 ` Eric D. Mudama
2003-12-31 19:13 ` Andy Isaacson
2003-12-29 20:36 ` Jeff Garzik [this message]
2003-12-30 12:14 ` [PATCH] 2.6.0 - Watchdog patches Paul Jackson
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=3FF0903F.1030604@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@osdl.org \
--cc=wim@iguana.be \
/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.