On Jul 30, 2008, at 1:23 AM, Grzegorz Kossakowski wrote:
Any chance for you to create a similar page documenting your new approach? I'm sure that there would be a people benefiting from a nice cook-book document.
Gladly. Once I get it worked out, I'll document it (maybe Daisy would be the place for that).
Interesting. I'm not sure but when we have discussed Git advantages over svn on infrastructure lists that point has not been discussed.[...snip]Even if only for that purpose it makes sense to provide Git clones of Apache repositories.
I agree!This morning I was worried that I gave too much background in my email. I thought "nobody will care enough to read through all this crap!" I'm glad people seem to recognize this as a valid use case, not just some goof-ball cowboy idea...
Anyway, I hope there will be other use-cases for Git at Apache...
Me, too... I think it's inevitable :-)
I would like to add only one note to Reinhard's answer:Various parts of Cocoon are now released independently so version numbers can be completely different. Anyway, in most cases it's ok if you just checkout certain module and patch it.
Right. I still have to figure out how I'm going to handle that in my git setup, but I think you and Reinhard have set me on the right track here.
Fortunately, repositories provided by Jukka track all these branches and tags for different modules so you will have no trouble with such setup.
Yes.
thanks a _lot_, MarkNo problem. Next time it's better to discuss such things publicly (yes, I'm sorry that I didn't respond to your e-mail - as usual lack of free time). :-)
Actually, the only reason I emailed you first was specificatlly that I didn't know how "publicized" Jukka wanted this to be. I mean it's no big secret, he posted it on infra, but... still I didn't want to be the one to say "hey everybody... git party at Jukka's server!" :-) I guess he did say he could probably handle a few hundred users...
cheers, —ml—
smime.p7s
Description: S/MIME cryptographic signature
