From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: Kernel version of Arnaldos Net Git tree
Date: Tue, 21 Aug 2007 06:38:04 +0000 [thread overview]
Message-ID: <200708210738.05395@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570708191944j789a4e31u9ef23d55512e420b@mail.gmail.com>
Ian, Leandro
I fully sympathise with your experiences, having just been through much hell of
rebasing the test tree to track Arnaldo's recent changes (dont' worry, it works
and I will post the changes) and then finding out that 2 out of 3 computers no longer
even boot due to changes somewhere else in the tree.
I am open to suggestions as to when to resynchronise the tree.
What I will do, in any case, is put up a diff from a working version online.
The test tree was synchronised yesterday against davem-2.6
Gerrit
Quoting Ian McDonald:
| > I tested using Linus and David Miller and the problem of watchdog
| > didn't happen. But using both Arnaldo or Gerrit I got the watchdog
| > problem! :( How often gerrit sync his git repository into Arnaldo git
| > and how often Arnaldo do this into David Miller netdev git tree?
| >
| > Leandro.
| >
| If it's any consolation then I went to test on one of my machines and
| it won't boot either. I'm running an older version of Gerrit's tree
| modified a lot (for faster restart testing).
|
| So I'll try doing the same sort of thing as you too now, but first
| I'll try Gerrit's more recent tree. Basically Gerrit and Arnaldo and
| Dave sync their trees when they feel like it. Generally before
| submitting upstream people tend to resync to check their patches still
| apply. Gerrit and Arnaldo and I will often sync off Dave M's release+1
| tree (currrently 2.6.24) as this is where networking changes go if the
| merge window is not currently open (Linus only allows changes up to
| rc1 of any release).
|
| What you and I might have to do is take Gerrit's tree and pull his
| changes out of the tree (they are the most recent patches) and apply
| them to Linus' latest tree. I don't know the syntax for this yet but
| will tell you if I have to do this (please tell me the syntax if you
| do it first!!). We will need Linus' tree rather than Dave
| M's/Arnaldo's tree (even if they rebase) as at the moment with
| Arnaldo's recent patch set I'm pretty sure Gerrit's patches won't
| apply cleanly any more until he reworks his patch set. The joys of
| distributed development!
next prev parent reply other threads:[~2007-08-21 6:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 2:44 Kernel version of Arnaldos Net Git tree
2007-08-20 2:46 ` Ian McDonald
2007-08-20 2:54 `
2007-08-20 2:57 ` Ian McDonald
2007-08-20 3:13 `
2007-08-20 3:14 `
2007-08-20 22:36 ` Ian McDonald
2007-08-21 0:04 ` Ian McDonald
2007-08-21 6:38 ` Gerrit Renker [this message]
2007-08-21 7:16 ` Ian McDonald
2007-08-21 7:37 ` Gerrit Renker
2007-08-21 18:41 `
2007-08-21 19:11 ` Gerrit Renker
2007-08-21 21:08 ` Ian McDonald
2007-08-22 9:00 ` Gerrit Renker
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=200708210738.05395@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@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