take messages

take messages

[Christoph Hellwig]

folks, any chance to get take messages sent to the list, please?  Kust
saw the tree is merged up to 2.6.25 (why not .26-rc, btw?) and there's
been no take message sent to the list again..

Re: take messages

[Mark Goodwin]

Christoph Hellwig wrote:
> folks, any chance to get take messages sent to the list, please? 

do you mean for any checkin, or just oss pushes?

> Kust
> saw the tree is merged up to 2.6.25 (why not .26-rc, btw?) and there's
> been no take message sent to the list again..
> 

Lachlan was held up with QA failures on updating the internal dev tree,
which was in turn holding up .26-rc I think.

Lachlan, what's the status with this?

Thanks

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

Re: take messages

[Christoph Hellwig]

On Mon, May 19, 2008 at 10:30:32AM +1000, Mark Goodwin wrote:
> Christoph Hellwig wrote:
> >folks, any chance to get take messages sent to the list, please? 
> 
> do you mean for any checkin, or just oss pushes?

Well, the oss pushes are automatic, so it should be sent with the
actual commit.  Even better would be migrating XFS to a proper git
tree with a commit trigger so that people can't accidentally forget it..

Re: take messages

[Lachlan McIlroy]

Christoph Hellwig wrote:
> On Mon, May 19, 2008 at 10:30:32AM +1000, Mark Goodwin wrote:
>> Christoph Hellwig wrote:
>>> folks, any chance to get take messages sent to the list, please? 
>> do you mean for any checkin, or just oss pushes?
> 
> Well, the oss pushes are automatic, so it should be sent with the
> actual commit.  Even better would be migrating XFS to a proper git
> tree with a commit trigger so that people can't accidentally forget it..

oss pushes automatic?  They could be but aren't.  Yes, migrating XFS
to a git tree is a great idea - one we have been talking about for
far too long...

Re: take messages

[Christoph Hellwig]

On Tue, May 20, 2008 at 11:50:16AM +1000, Lachlan McIlroy wrote:
> oss pushes automatic?  They could be but aren't.

They aren't?  Back in the days the CVS tree on OSS was updated from
ptools once a day.

Re: take messages

[Mark Goodwin]

Christoph Hellwig wrote:
> On Tue, May 20, 2008 at 11:50:16AM +1000, Lachlan McIlroy wrote:
>> oss pushes automatic?  They could be but aren't.
> 
> They aren't?  Back in the days the CVS tree on OSS was updated from
> ptools once a day.
> 

The ptools->cvs push is automatic. The git updates are not.
We have a plan to fix that ... just catching our breath a bit
at the moment.

Cheers

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

Re: take messages

[Russell Cattelan]

Mark Goodwin wrote:
>
>
> Christoph Hellwig wrote:
>> On Tue, May 20, 2008 at 11:50:16AM +1000, Lachlan McIlroy wrote:
>>> oss pushes automatic?  They could be but aren't.
>>
>> They aren't?  Back in the days the CVS tree on OSS was updated from
>> ptools once a day.
>>
>
> The ptools->cvs push is automatic. The git updates are not.
> We have a plan to fix that ... just catching our breath a bit
> at the moment.
ptools to oss cvs is done once every hour.
Which is probably a bit silly now given updates come from the CA ptools 
server
and most XFS commits probably originate at the AU server. If I recall 
correctly
the AU <-> CA ptools sync is only once a day.

There is also the xfs git and the dmapi git trees that are auto synced 
with the
cvs tree once a day.  (minus the autoversion stuff)
>
> Cheers
>

Re: take messages

[Lachlan McIlroy]

Mark Goodwin wrote:
> 
> 
> Christoph Hellwig wrote:
>> folks, any chance to get take messages sent to the list, please? 
> 
> do you mean for any checkin, or just oss pushes?
> 
>> Kust
>> saw the tree is merged up to 2.6.25 (why not .26-rc, btw?) and there's
>> been no take message sent to the list again..
>>
> 
> Lachlan was held up with QA failures on updating the internal dev tree,
> which was in turn holding up .26-rc I think.
> 
> Lachlan, what's the status with this?

It was a big TAKE message so it was probably dropped on the floor
somewhere.

Updates to the internal dev tree are dependent on the kdb patches
and at the time they were only available for 2.6.26-rc1.  2.6.25
was a more stable choice.  We usually wait until -rc3 for an update
so as soon as the kdb patches are available I'll do another merge.