From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: BK to GIT migration status for ia64
Date: Fri, 29 Apr 2005 09:41:26 +0000 [thread overview]
Message-ID: <17010.326.499746.341125@napali.hpl.hp.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F035ECFEA@scsmsx401.amr.corp.intel.com>
>>>>> On Thu, 28 Apr 2005 12:19:49 -0700, "Luck, Tony" <tony.luck@intel.com> said:
Tony> It's been a hectic month (well, not even a month ... this
Tony> is only day 24 of the great migration :)
Tony> I've set up a pair of GIT trees on kernel.org for ia64 to
Tony> keep track of changes.
Tony> 1) rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git
Tony> This is the "to-linus" tree. Anything commited here is queued to go
Tony> into Linus' tree next time he does a pull from me. Some obviously
Tony> correct (to me) patches will go directly into this tree, but most
Tony> patches will spend time in the test tree.
Tony> 2) rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/test-2.6.git
Tony> This is the "to-andrew" tree. Andrew has a script to pull
Tony> automatically from here, so changes in this tree will usually
Tony> end up in the next "-mm" patch.
Looking good so far. Of course, I'm still waiting to see what happens
when attempting a first non-trivial merge...
Tony> I'm not going to play games renaming these trees each release (pauses
Tony> to wait for cheering to die down) this didn't really work for me the
Tony> way it did for Len (from whom I stole the idea) because my workflow
Tony> isn't quite the same.
Excellent. Might have to wait for a _long_ while for the applause to
die down... ;-)
--david
next prev parent reply other threads:[~2005-04-29 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 19:19 BK to GIT migration status for ia64 Luck, Tony
2005-04-29 9:41 ` David Mosberger [this message]
2005-05-01 4:19 ` Keith Owens
2005-05-02 11:47 ` David Mosberger
2005-05-02 12:59 ` Keith Owens
2005-05-02 17:09 ` Luck, Tony
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=17010.326.499746.341125@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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