Probably the simplest way to achieve this is with git archive
. If you really need just the expanded tree you can do something like this.
git archive master | tar -x -C /somewhere/else
Most of the time that I need to 'export' something from git, I want a compressed archive in any case so I do something like this.
git archive master | bzip2 >source-tree.tar.bz2
ZIP archive:
git archive --format zip --output /full/path/to/zipfile.zip master
git help archive
for more details, it's quite flexible.
Be aware that even though the archive will not contain the .git directory, it will, however, contain other hidden git-specific files like .gitignore, .gitattributes, etc. If you don't want them in the archive, make sure you use the export-ignore attribute in a .gitattributes file and commit this before doing your archive. Read more...
Note: If you are interested in exporting the index, the command is
git checkout-index -a -f --prefix=/destination/path/
(See Greg's answer for more details)
Best Answer
I realize that a half year has passed, however this question returns quite often and I hope someone will find my answer usefull.
Native output for SSRS 2005 is usually reffered as the WebForm and this is basically what SSRS is suppose to produce. The thing is that often users wants to have the report in other form and thats why exporting (translation) has been added. The problem here is that it isnt generating output directly to desired form, but it creates a webform that is beeing processed and translated to another format (thus additional issues/limitations).
While the official answer from the MS representatives is that you need to have MS SQL 2012 (which I can understand - as there's a matter of official support, company internal policy etc.) there is a number of ways allowing us to archive that goal.
It mostly depends on a reason why you want to have it in xslx. Most often it is just because of (big table in report) xls rows/colums limitations.
What can you do?
Get 3rd party plugin (someone already seen this as a potential benefit - there are example links in article at URL 1
Configure your own defined renderer - described at URL 2, but requires you to have translation engine
Use VBA in Excel 2007 file to import data (as xls or csv) and save it as you like it.
Use workaround - make your tables the way they fit into Excel 2003 restrictions. eg. in case of too many rows (described at URL 3):
URL 1 - social.msdn.microsoft.com/Forums/sqlserver/en-US/9d8cd766-ff78-490f-8a5d-bb4a0debdfc1/export-ssrs-2005-report-to-excel-2007
URL 2 - www.traviata.eu/blogs/technical/?p=435
URL 3 - www.sqlservercentral.com/Forums/Topic554766-150-1.aspx