From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: 2.6.19-rcX vs 2.6.20
Date: Tue, 24 Oct 2006 08:12:17 +0000 [thread overview]
Message-ID: <200610240912.18076@strip-the-willow> (raw)
In-Reply-To: <200610240848.47708@strip-the-willow>
Hi Arnaldo,
| I guess I should just create a net-2.6.20 git tree to fix this
| situation, but I guess you guys could also maintain git trees
| somewhere, so that I could pull from you, what do you think?
If that would make the situation better, I'll do that. We've got
web servers and the like here. So ... that would be like
* patches sent to Arnaldo for checking
* Arnaldo merges into his 2.6.20 tree
* Gerrit (or Ian or Andrea) pulls Arnaldos changes
* whoever pulled last, keeps it consistent with netdev tree
* next time patches come in for revision, Arnaldo can pull
from the up-to-date tree
* or ... ?
That would be great - these patches are just in the way to get other
work done.
Gerrit
next prev parent reply other threads:[~2006-10-24 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 7:48 2.6.19-rcX vs 2.6.20 Gerrit Renker
2006-10-24 7:53 ` Arnaldo Carvalho de Melo
2006-10-24 8:12 ` Gerrit Renker [this message]
2006-10-24 8:23 ` Ian McDonald
2006-10-24 8:54 ` 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=200610240912.18076@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 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.