Git Modularization example Boost .gitattributes
Shouldn't the repositories contain a .gitattributes file indicating the eol flavor to be used for text files where it has significance?
Perhaps! I don't know anything about .gitattributes. Where can I find out more?
Dave, I can probably save you some work here with my "perfect" mirror of Boost's EOL and MIME type config into a .gitattributes with which I configured my subgit to mirror my git repo into Boost sandbox. Taken from https://github.com/ned14/TripleGit/blob/master/.gitattributes: * text=auto !eol svneol=native#text/plain *.gitattributes text svneol=native#text/plain # Scriptish formats *.bat text svneol=native#text/plain *.bsh text svneol=native#text/x-beanshell *.cgi text svneol=native#text/plain *.cmd text svneol=native#text/plain *.js text svneol=native#text/javascript *.php text svneol=native#text/x-php *.pl text svneol=native#text/x-perl *.pm text svneol=native#text/x-perl *.py text svneol=native#text/x-python *.sh eol=lf svneol=LF#text/x-sh configure eol=lf svneol=LF#text/x-sh # Image formats *.bmp binary svneol=unset#image/bmp *.gif binary svneol=unset#image/gif *.ico binary svneol=unset#image/ico *.jpeg binary svneol=unset#image/jpeg *.jpg binary svneol=unset#image/jpeg *.png binary svneol=unset#image/png *.tif binary svneol=unset#image/tiff *.tiff binary svneol=unset#image/tiff *.svg text svneol=native#image/svg%2Bxml # Data formats *.pdf binary svneol=unset#application/pdf *.avi binary svneol=unset#video/avi *.doc binary svneol=unset#application/msword *.dsp text svneol=crlf#text/plain *.dsw text svneol=crlf#text/plain *.eps binary svneol=unset#application/postscript *.gz binary svneol=unset#application/gzip *.mov binary svneol=unset#video/quicktime *.mp3 binary svneol=unset#audio/mpeg *.ppt binary svneol=unset#application/vnd.ms-powerpoint *.ps binary svneol=unset#application/postscript *.psd binary svneol=unset#application/photoshop *.rdf binary svneol=unset#text/rdf *.rss text svneol=unset#text/xml *.rtf binary svneol=unset#text/rtf *.sln text svneol=native#text/plain *.swf binary svneol=unset#application/x-shockwave-flash *.tgz binary svneol=unset#application/gzip *.vcproj text svneol=native#text/xml *.vcxproj text svneol=native#text/xml *.vsprops text svneol=native#text/xml *.wav binary svneol=unset#audio/wav *.xls binary svneol=unset#application/vnd.ms-excel *.zip binary svneol=unset#application/zip # Text formats .htaccess text svneol=native#text/plain *.bbk text svneol=native#text/xml *.cmake text svneol=native#text/plain *.css text svneol=native#text/css *.dtd text svneol=native#text/xml *.htm text svneol=native#text/html *.html text svneol=native#text/html *.ini text svneol=native#text/plain *.log text svneol=native#text/plain *.mak text svneol=native#text/plain *.qbk text svneol=native#text/plain *.rst text svneol=native#text/plain *.sql text svneol=native#text/x-sql *.txt text svneol=native#text/plain *.xhtml text svneol=native#text/xhtml%2Bxml *.xml text svneol=native#text/xml *.xsd text svneol=native#text/xml *.xsl text svneol=native#text/xml *.xslt text svneol=native#text/xml *.xul text svneol=native#text/xul *.yml text svneol=native#text/plain boost-no-inspect text svneol=native#text/plain CHANGES text svneol=native#text/plain COPYING text svneol=native#text/plain INSTALL text svneol=native#text/plain Jamfile text svneol=native#text/plain Jamroot text svneol=native#text/plain Jamfile.v2 text svneol=native#text/plain Jamrules text svneol=native#text/plain Makefile* text svneol=native#text/plain README text svneol=native#text/plain TODO text svneol=native#text/plain # Code formats *.c text svneol=native#text/plain *.cpp text svneol=native#text/plain *.h text svneol=native#text/plain *.hpp text svneol=native#text/plain *.ipp text svneol=native#text/plain *.tpp text svneol=native#text/plain *.jam text svneol=native#text/plain *.java text svneol=native#text/plain Hope that's useful. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.
on Fri May 24 2013, Niall Douglas
Shouldn't the repositories contain a .gitattributes file indicating the eol flavor to be used for text files where it has significance?
Perhaps! I don't know anything about .gitattributes. Where can I find out more?
Dave,
I can probably save you some work here with my "perfect" mirror of Boost's EOL and MIME type config into a .gitattributes with which I configured my subgit to mirror my git repo into Boost sandbox. Taken from https://github.com/ned14/TripleGit/blob/master/.gitattributes:
<snip>
Hope that's useful.
Very much so! I've arranged to have it injected into the root of every converted Git repository. It's missing from http://github.com/boostorg/boost at the moment but I hope once http://jenkins.boost.org/job/Boost2Git/2119 completes, it'll be there. Would you be willing to work with Boosters to correct any related line-ending/MIME issues? I'll happily give you commit rights to the repository at https://github.com/ryppl/Boost2Git/blob/master/dot_gitattributes -- Dave Abrahams
I can probably save you some work here with my "perfect" mirror of Boost's EOL and MIME type config into a .gitattributes with which I configured my subgit to mirror my git repo into Boost sandbox. Taken from https://github.com/ned14/TripleGit/blob/master/.gitattributes:
<snip>
Hope that's useful.
Very much so! I've arranged to have it injected into the root of every converted Git repository. It's missing from http://github.com/boostorg/boost at the moment but I hope once http://jenkins.boost.org/job/Boost2Git/2119 completes, it'll be there.
Great. Glad it was useful.
Would you be willing to work with Boosters to correct any related line- ending/MIME issues? I'll happily give you commit rights to the repository at https://github.com/ryppl/Boost2Git/blob/master/dot_gitattributes
Happy to help. As a related question, myself and Paul are hoping to have proposed Boost.AFIO sandbox ready for GSoC Milestone 1 end of this month. Do we still submit to Boost.Sandbox SVN and let that mirror to Git, or seeing as it's already in GIT at https://github.com/BoostGSOC do we use some method of mirroring that directly to Git Modular Boost? Thanks, Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.
on Mon Jul 15 2013, Niall Douglas
I can probably save you some work here with my "perfect" mirror of Boost's EOL and MIME type config into a .gitattributes with which I configured my subgit to mirror my git repo into Boost sandbox. Taken from https://github.com/ned14/TripleGit/blob/master/.gitattributes:
<snip>
Hope that's useful.
Very much so! I've arranged to have it injected into the root of every converted Git repository. It's missing from http://github.com/boostorg/boost at the moment but I hope once http://jenkins.boost.org/job/Boost2Git/2119 completes, it'll be there.
Great. Glad it was useful.
And... it's there now.
Would you be willing to work with Boosters to correct any related line- ending/MIME issues? I'll happily give you commit rights to the repository at https://github.com/ryppl/Boost2Git/blob/master/dot_gitattributes
Happy to help.
Done, thanks.
As a related question, myself and Paul are hoping to have proposed Boost.AFIO sandbox ready for GSoC Milestone 1 end of this month. Do we still submit to Boost.Sandbox SVN and let that mirror to Git, or seeing as it's already in GIT at https://github.com/BoostGSOC do we use some method of mirroring that directly to Git Modular Boost?
I don't think you need to do any mirroring at all, unless you submit it for review and there's some kind of official policy that all reviews have to use Boost's SVN sandbox... and even if there is, we might want to change that policy before your review date. I'd say, sit tight for now, and ask the Review Wizards when you apply for the review whether you need to change something. -- Dave Abrahams
As a related question, myself and Paul are hoping to have proposed Boost.AFIO sandbox ready for GSoC Milestone 1 end of this month. Do we still submit to Boost.Sandbox SVN and let that mirror to Git, or seeing as it's already in GIT at https://github.com/BoostGSOC do we use some method of mirroring that directly to Git Modular Boost?
I don't think you need to do any mirroring at all, unless you submit it for review and there's some kind of official policy that all reviews have to use Boost's SVN sandbox... and even if there is, we might want to change that policy before your review date. I'd say, sit tight for now, and ask the Review Wizards when you apply for the review whether you need to change something.
Ok, I'll drop a line to the Review Wizards now to give them a heads up. We're actually intending something a bit different for Milestone 1: we're going to ask this list (and boost-announce if we're allowed) for what are the most commonly desired new features. Right now, proposed AFIO is absolutely barebones, and there is a long list of what we /could/ add but we have no idea what is actually desired. For example, the existing AFIO dependency based write ordering enforcement mechanism currently has two implementations, one based on fsync() and the other based on O_SYNC, and neither of which are fast. BTRFS and ZFS [1] have the ability to O(1) snapshot the filing system and therefore enforce write ordering far, far more quickly. The question then becomes, is such a feature desirable enough to potential AFIO users that we choose implementing that over let's say, a special Linux kaio driver whose sole benefit is to reduce thread count overheads on Linux to the same level as Windows? Anyway that's still a week or two out. Got to get Jenkins working with all major C++11 compilers on all supported platforms first. That's Paul's next job for this week. Thanks Dave. Niall [1]: Neither BTRFS nor ZFS do O_DIRECT well (ZFS simply refuses), which makes O_SYNC performance even worse. An alternative write ordering enforcement for these COW based filing systems is therefore especially attractive. --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.
participants (2)
-
Dave Abrahams
-
Niall Douglas