Skip to contentSkip to conversation

take messages

DISCUSSION Christoph Hellwig 5 participants 8 messages May 18, 2008 – May 20, 2008

lore
Share & tools
lore
#0 lore raw

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..

#1 lore raw
Quoted 1 line · Christoph Hellwig

folks, any chance to get take messages sent to the list, please?

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

Quoted 4 lines

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

Signature · 4 lines
 Mark Goodwin                                  [email protected]
 Engineering Manager for XFS and PCP    Phone: +61-3-99631937
 SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------
#2 lore raw
Quoted 4 lines · Mark Goodwin
Quoted 1 line · Christoph Hellwig

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..

#7 lore raw
In reply to Mark Goodwin
Quoted 12 lines · Mark Goodwin
Quoted 1 line · Christoph Hellwig

folks, any chance to get take messages sent to the list, please?

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

Quoted 4 lines

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..

Quoted 4 lines

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.

#3 lore raw
In reply to Christoph Hellwig
Quoted 8 lines · Christoph Hellwig
Quoted 3 lines · Mark Goodwin
Quoted 1 line · Christoph Hellwig

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...

#4 lore raw
Quoted 1 line · Lachlan McIlroy

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.

#5 lore raw
Quoted 6 lines · Christoph Hellwig
Quoted 1 line · Lachlan McIlroy

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

Signature · 4 lines
 Mark Goodwin                                  [email protected]
 Engineering Manager for XFS and PCP    Phone: +61-3-99631937
 SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------
#6 lore raw
Quoted 6 lines · Mark Goodwin
Quoted 3 lines · Christoph Hellwig
Quoted 1 line · Lachlan McIlroy

oss pushes automatic? They could be but aren't.

Quoted 7 lines
Quoted 3 lines

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)

Quoted 3 lines

Cheers