text:
Directed by: Christopher Nolan
Written by: Christopher Nolan
Company: Warner Bros. Pictures, Legendary Pictures, Syncopy
Runtime: 148 minutes
The film is about Dom Cobb, a man wanted for arrest in his home country because of his job, extraction, a job involving stealth where a person enters other person's subconscious in his dreams. He wanted to go home, but because he is on the blacklist of passengers entering his home country, he cannot go home. An offer from Saito, a rich businessman who wanted to do inception in his business, forced him to do something that he did not really want to do, but he did, guaranteed that Saito will be in-charge of his return to home.
In this task, he is joined by Arthur, his partner, Ariadne, an architecture graduate, Eames, an associate, and Yusuf, the chemist. Their subject is Robert Fishcer, the heir of a business magnate who is having some issues with his father. To implement the plan, they subjected Robert and themselves to heavy sedation. In the execution of the job, some things go wrong, complicating things.
This is why movies are made.
The direction is as great as you can get. Christopher Nolan – what kind of brain does he have? He holds the whole film right from the start until the last second of with with such immense glory and pulling force that it is simply remarkable. You can see the intelligence through the display of stunning bedazzlement that only a master filmmaker can do. It's overwhelming, it's astounding. The moviemaking process itself is a big mystical puzzle that Nolan was able to accomplish with the cinematic power that results to a majestic experience.
It was indeed an experience, an experience like no other. It was a rousing roller-coaster ride that brought filmmaking to new heights. It was able to push the boundary between reality and magic. And there is also the very wise usage in capturing the right pace for this movie. A lot of time in the first part was used for introductions and plot developments. It may seem tedious to go through in paper, but Nolan is a genius. He was able to sustain a dynamic stream that continues throughout the parts of development until we reach the action scenes where we see more of his directorial prowess.
And then come the final act of the film. It's a breathtaking, earth-shattering part of the film where we all see the peak of the film. This part is unlike anything that I have ever seen before. It's an indescribable part of this already unforgettable film, and this is where we just let the director take charge in all of the events that unfold.
The screenplay is as original as you can get. It's almost flawless. You can say things about the characters being used as plot devices, but who cares? The story is puzzling, but when you rewatch it, the genius of the screenplay unfolds like magic. There is a big amount of complexity in it that you can't get with just one time of watching. Truth be told, I watched this like four to seven times before I fully got this movie. And when you already understand the whole, you can only reckon the high level of intelligence contained in this movie. It's mindblowing.
The cinematography was fantastic. Looking back, there were very few stylized shots in this film, but the function that it served in the film was indeed vital. It is quite noticeable that the film used a fair amount of handheld shots, quite unusual for a big movie like this. Anyway, putting the big shots aside, the cinematography was able to bring the story and the characters closer to the audience. In this massive story of epic proportions, it is quite hard to channel these characters who are almost of second importance to the plot, but somehow, the angles, the shots, the colors, the shades, were able to actually absorb us to the film.
The editing is superb. When I watch the film, I know that I'm always into something that I should watch out. Even the simple exchange of words, there is the feeling that something is about to happen in about a few moments. There's always this on-the-edge feeling throughout the film, and that's mainly due to the film. The actions scenes are composed in a way that's quite different than the normal action scenes from standard action films. The dramatic scenes never felt out-of-place, and always affecting. The final third act is the editing's crowning glory, bringing all the skills that the editor has. By the end of the film, I felt that I went one big roller-coaster ride. And wow, was it that thrilling.
The sound must be heard to be believed. This may seem to be the least evident component of the filmmaking process, but in this film, it was so important. It created the world aside from the visuals. The whole move felt like you were really in the place, and that says a lot in a film like this. It's as if you are inside this whole movie and it's as exhilarating as movies can be. It's so detailed, yet it never gets annoying. And how it gave emphasis to each sound but all of those still feel like it's one, not separate from each other.
The musical score is GREAT! What could I say? Right from the start, it already was able to set the film to a higher degree of truth. You know you are up to something, but the music never abused itself to drown to film to its strong power. And with the start of the first action scene, what comes next is the film's majestic prowess unleashed, adding a lot to the film's already atmospheric milieu. The power of the music lies on the fact that it went so well with the visuals. It's breathtaking, but it's so because of the visuals.
Impeccable the production design is. There is nothing in everything that you see in the film that you may think is not well-thought of. The rooms present in the dream scenes are beautifully designed, but some very small details in it provide the air of surrealism in it. It could have been that it's too beautiful, but it's never obvious. It underlines every single thing that it wants to tell, bu the message it suggests is present. The different levels of dream give a big challenge on the designers because it should be defined from the other levels of dream. And with some of the most surprising sets (fortress, hallway), and knowing that they're all real, I'm just impressed.
The visual effects are high class. There is no visual effect shot in the film that looked fake. None whatsoever. It's so real. Of course, you know that the shot was CGI because you know it's very much impossible to do (the glacial style of collapse of the buildings), but there are also shots where you expect that CGI will take over, but when you watch the process, it's surprising that it was an on-set effect. Take the collapse of the fortress. I was pretty much sure that it was CGI, until I found out that it wasn't. It's just so confusing if you're watching CGI or completely on-set effects. Either way, it was enchanting.
What do you have if you have a big ensemble cast with this high caliber of actors giving top-notch performances?
Leonardo DiCaprio is good and surprisingly touching as Dom Cobb. I felt for his confusions, for his desperation, for his affliction. Not to mention that the grief part of his performance is beautifully understated.
Cillian Murphy is heartbreaking as Robert Fischer, Jr. He's got a lot of conflict in him, and he does not have the biggest amount of time to channel that to us, but in this one small bit of a performance, he was able to give us the film's most touching scene – his farewell to his father. It just gave a sudden eruption of emotions from me. Anyway, moving on.
Marion Cotillard is excitingly dangerous as the film's heart, Mal. There is this breeze of fatality whenever she appears on screen. She's the most unpredictable of all the characters because she does not have a mind of her own. She is the product of Dom's dark past. She can kill you with one sharp stare, but she can also break your heart with that same eye. And only a skillful actress like Cotillard could handle that tricky job.
Ellen Page – there's nothing wrong with her, actually. I can't see anything wrong with her performance. Actually, she was fine with her role. Not in the same caiber as Cotillard, but she did fine.
Joseph Gordon-Levitt, Tom Hardy, Michael Caine, Tom Berenger, and Dileep Rao provide strong supporting work in their roles.
But in the end of the journey with this film, it's Christopher Nolan. He is the star of this film, and all the praises of this film should be unto him. Without Nolan, this film's nothing. This is his crown, and this year's crown. When we look back at this year twenty years from now or so, we'll still remember this film. I'm pretty much sure on that.
For this, the movie gets:
What are your thoughts? Do you agree or not?


text:
Since we were earthed and birthed in 2000 our food has been highly nurtured and well natured. Our service has grown and matured into one of London's prime, meaty, yet tender caterers.
Our ingredients come from researched backgrounds, they are appraised, tried and tested. We only use the best and freshest produce sourced from London's main markets and reputable suppliers. Some are local, some have come from afar but all are welcomed into our kitchen with desire and tenderness, where we make everything from start to finish.
We look for the same qualities and give and expect the same from our staff. Training is hard, passionate and educational, with controls, stops and balances at every stage: our mantra - only the best will succeed. Our inspired and experienced cooks blossom and grow into fine creative chefs. Their hands create fresh, generous, delightful dishes that find their way into London's top boardrooms, business meetings, and VIP events.
We are proud of the food we produce and event service we offer. We thank our staff for the long hours, dedication and commitment - which means the quality, consistency and presentation always shines through for our customers.

subset: commoncrawl


text:
I am not a licensed nutritionist, dietician or fitness trainer. Views expressed on this website are based on my own personal research and experiences. Please consult with your doctor regarding any concerns you may have regarding your health.
In October I started looking into gluten, how it may or may not affect our health and how we feel and who should be on a gluten free diet. Wow! I had no idea! What caught my attention immediately was the connection between gluten and thyroid disease. I've been on medication for years for hypothyroidism so I have decided to explore the possibility of how the foods I eat (specifically gluten) might affect thyroid functioning. Who knows? Maybe I can make a change and as a result stop taking the medication all together or reduce the amount I have to take. That brings us to the
2014 #MakeAChange Challenge
When does the challenge start?
==> January 6, 2014
What is the challenge?
==> Commit to 21 days of a diet change of your choice. Challenge yourself. By challenge, I do not mean a competition or a "you must lose this much weight" effort. I mean, we come together in a positive, supportive, non-judgmental way to really make some changes that will positively influence your health.
Why should I join this challenge?
==> Making total changes to your diet can be overwhelming. Making one small change for a short period of time is doable and may lead to feeling better and better health.
==> Obviously there's no such thing as a perfect diet. Biochemically, we're all unique and have individual needs for how much to eat, what to eat, and when to eat. Not to mention the fact that there are social and psychological components to eating well. We're all here to do our best to find our individual best nutrition/lifestyle match.
How do I participate?
==> Sign up by completing the form below. There will be a place for your name, email, goal and blog address (optional). You must put in a name and email. If you have a blog please add it so we can create a Make A Change blogroll.
==> At the beginning of the challenge decide what change YOU would like to make to your diet and set a goal. You know where your are nutritionally and where you want to be!
==> Mark your calendars! Leave a comment [on this post] on Fitness, Health and Happiness on January 6, 13, 20 and 27th with your update/progress for that week. When you come leave a comment with your goal/check-in you will be entered to win one of the prizes each week!
My personal "Make A Change" will be to go gluten free for at least the duration of the challenge and if all goes well I will continue for 3 months.
"…researchers found that…organ-specific autoantibodies (i.e., thyroid antibodies) — will disappear after 3 to 6 months of a gluten-free diet."
During the challenge I will share my experience, information, recipes and resources as it all relates to being gluten free.
What's a challenge without a badge? Feel free to use it on any and all social networks…or not.
If you have any questions please feel free to contact me via the Contact Jill tab above in the menu bar or at email@example.com.
Tell your friends and family! Tweet #MakeAChange, pin the image on your Pinterest boards and share the announcement on Facebook!


text:
Welcome, Guest
You searched for Industrial Filters. We've found 13 items for you.
High efficiency, below ground filtration system.
High efficiency, below ground filtration system. This model ships with a cast iron lid for vehicle loading applications.
Industrial duty, high efficiency, self-cleaning, below ground filtration system.
Industrial duty, high efficiency, self-cleaning, below ground filtration system. This model ships with a cast iron lid for vehicle loading applications.
External self-cleaning cascade filter for mechanical rooms and underground vaults supplying underground cisterns. Suitable for flows up to 5,000 GPM.
Rainwater from the roof is evenly distributed across a stainless steel filter mesh where the natural process of surface tension directs the cleaned water to the storage tank. The centrifugal rainwater filter can filter up to 5,500 square feet of roof area for irrigation, toilet flushing, vehicle washing, fire protection and other non-potable water uses. The 20 inch extension tube can be included, simply check the box below to receive.
The price is a non-discountable final sales price.
The Graf Choke Drain Shaft offers controlled outflow to the infiltration, detention or sewer system with parallel emergency overflow capability.
The Graf Infiltration Filter Shaft offers surface water pre-filtration and emergency stormwater overflow for swale ditch, retention and storage system applications.
Commercial screened rain heads prevent leaves and debris from blocking downspouts and entering your rainwater tank. Rain heads are ideally installed on each downpipe as they protect the building and improve your tank's water quality. 6 inch outlet size.
Internal basket filtration system to clean the rainwater inside the tank riser. Space-saving filter technology integrated in the tank – only 1 cover in the garden.
Rain Harvesting Pty Downspout First Flush Diverter
Rain Harvesting Pty Original Leaf Eater Downspout Filter
Recycled/Reclaimed Water ID Tag (Purple - Bilingual)
The RainHarvesting® First Flush Downspout Diverter. A simple and effective first flush water diverter that requires minimal maintenance.
The ultimate high performance self-cleaning downspout filter...improves water quality and reduces tank maintenance. By screening leaves onto the ground, the Leaf Eater prevents gutters from blocking and eliminates a fire hazard.
Purple Recycled/Reclaimed Valve and ID Tag - Bilingual. Great for hose bibs and water valves.
Rainflo 18 GPM Complete UV Disinfection System
Graf EcoBloc Light Modular Water Storage System
500 Gallon Complete Above Ground Rainwater Collection System
Viqua Integrated Home Rainwater Purification System, 12 GPM
Snyder 2500 Gallon SUNSHIELD Vertical Water Storage Tank
RainFlo MHP75A .75 HP Automatic Pump
RainFlo 430-AG Rainwater Collection System
Featuring superior performance, this complete UV disinfection system will treat rainwater directly from the storage tank and bring it up to fully potable standards, for reuse indoors.
Graf EcoBloc Light modular water storage systems feature unlimited storage capacity, flexible design options, ease of inspection and integrated filtration shafts. EcoBloc is today's leading solution for rainwater storage, stormwater detention and hybrid retention/detention installations. $61.90 price is for a single starter unit with Primary Module and Baseplate holding 66.0 US gallons. Please call 800-654-9283 for additional configuration and freight pricing.
The 500 Gallon Complete Above Ground Rainwater Collection System includes everything, mostly pre-assembled, for added 'plug and play' convenience, required for a complete rain harvesting and reusing system.
The Viqua 12 GPM Integrated Home Rainwater Purification System treats and disinfects rainwater for indoor use.
The SUNSHIELD water storage tank is available in dark green, black and sand to blend with the environment, provide additional protection from UV rays and reduce algae growth. Standard configuration includes threaded lid as well as factory installed fill and drain.
RainFlo automatic .75 horsepower pumping system with durable and quiet performance up to 26 GPM and 65 PSI (max.)
RainFlo 430 gallon above ground rainwater collection system. Includes everything needed for a complete rain harvesting system.
Graf 350 Gallon Top Tank
RainFlo Double Rainwater Purification Package, 30 GPM
Norwesco 1350 Gallon Above Ground Water Tank - Green
Graf Mondo 137 Gallon Rain Barrel
Leader Divertron 1000 Automatic Submersible Pump
RainFlo 1700-IG Rainwater Collection System
RainFlo Easy Bundle
RainFlo AGS Above Ground Rainwater Collection System
Graf Top Tank™ 350 Gallon Above Ground Water Tank
RainFlo 30 GPM Double Rainwater Purification Package - Treats and disinfects rainwater for indoor use
The 1350 Gallon water storage tank is available in Black and Dark Green to blend with the environment, provide additional protection from UV rays and reduce algae growth. Includes 16" threaded lid, 1.5" inlet and a 2" drain with plug.
The Graf Mondo Rain Barrel is attractive and sturdy with internal steel support rods. Rectangular design is space-saving and fits neatly against a a wall or fence. The 137 gallon capacity is one of the largest rain barrels on the market. Shown with optional base.
Leader Divertron 1000 3/4 HP, 115V submersible automatic rainwater pump with integrated on/off control and run-dry protection. This model comes with screened inlet.
RainFlo 1700 gallon in-ground rainwater collection system. Includes everything needed for a complete rainharvesting system.
Package bundle with Calming Inlet, Overflow Siphon, 4" flexible pipe coupler and two 4" Multi-Tite gaskets for standard inlet and outlet plumbing of rainwater collection tanks. Package price saves over 10%.
RainFlo professional above ground rainwater collection system. You choose the tank and this above ground package includes everything else you need to construct your own rainwater collection system.


text:
Document Type
Conference Proceeding
Publication Date
Attendees will have an opportunity to learn and discuss with two librarians from California State University System about the challenges and issues experienced in implementing bilingual services in reference and instructional sessions to bilingual speaking students on their campuses. In addition, attendees will be able to learn about a strong partnership developed between both librarians as well as empowering a curriculum relationship with faculty in Foreign and Romance Languages Departments. Presenters will also address how to create an ambiance of support to first generation students who often experience a lack of confidence necessary to be academically successful.
After the presentation, the panelists will engage participants to discuss the following outcomes:
* Supporting and enhancing curriculum demands
* Sharing ideas with other colleagues, who use bilingual services in any language
* Finding similar strategies in other academic libraries
Recommended Citation
Eileen Bosch and Valeria Molteni. "Building and Designing Bridges - Enabling Bilingual Academic Learning Experiences" LOEX Conference Proceedings 2008 (2010).


text:
(git is wonderful. In the same way that unix is an'operating system done right', git is 'source control done right'.
It has a surprising history, being basically the creation of Linus Torvalds, who decided that all the available source control solutions were useless, and so just wrote his own. That is fabulously cool.
This is a small article to introduce you to git.
Learning Curve
There definitely is a learning curve with git. At least that was the case for me.
For starters, I had to throw away some concepts which I thought were set in stone. Git forces you to think about code in a different way. It turns out that that way of thinking has large advantages.
The single biggest mental stumbling block for me was that I always considered the real code, the precious bit, to be the one I'm currently working on, and the code that is in source control system to be a backup. A byproduct, so to speak. You need to completely overturn this with git.
The real stuff, the precious stuff, is what is in your repository. What you are currently working with, your working directory, that's something like a scrapbook. You're trying things out, making changes here and there, but it's all very temporary and it's not where the real stuff is. It shouldn't be frightening to overwrite your working directory, for instance.
Let me track back a while and introduce the three areas in a local git repository (I am not talking about a remote repository, I am talking about a local git repository, on your local hard drive, and blazingly fast).
The repository is where the history of your project is stored. It's quite similar to a series of snapshots of your whole project. Each of these snapshots contain your whole project (technically, git is not saving the whole project but just saving the delta to your initial commit, but conceptually, think of these snapshots as whole copies of your project).
These snapshots are called commits. They are unique, and can be referred to in a number of different ways, either directly (by using its number, which is a SHA-1 hash) or relatively (three commits before the last one I did).
Each commit points to a parent commit. When you have two different commits pointing to the same parent, these two commits are the starting points of different branches. The two codestreams, from this branching point, starts having a life of their own, although it's possible to merge different branches together at a later stage.
Decentralized weirdness
This is a good time to introduce another weirdness that took me some time to grok. There is no primacy between branches. It's a delightfully anarchic system, no bosses – a little like the anarcho-syndicalist communes of 'The Holy Grail'. There is no master control program, no centralized master system. One can define certain branches to be more 'important' than others, but it's just a naming convention, it's not something that is built in.
The same applies between your local repository and the remote repository. Git really doesn't assume that one of them is more important than the other. It's very disquieting, but liberating once you've understood it.
Working Directory
Next, your working directory. This is where your whole project is, where the code is, images, what have you. This is what gets 'snapshotted' each time one makes a commit. It could be possible to snapshot your whole project every time, i.e. every single file, but it turns out that that is a bad idea, because you end up saving too much and it gets really difficult to understand what exactly happened between two commits. I must admit to having done that at the beginning, because I was blocked in my 'backup' concept.
No, what you want to do is make lots of small commits, with each commit changing as few files as possible, as long as they pertain to one common change.
Staging Area
Enter the staging area. Really well named, this is where you determine which files you want to belong to the next commit. You're not interested in the files that have changed only because something trivial like a timestamp has changed, and you're not interested in unrelated changes either. You really want to encapsulate all the changes necessary for a single debugging or a single new feature into a commit.
The following diagram shows the basic logic: you add files to the staging area with the git add command, then you commit those added files with a git commit command. Bringing back a specific commit to the working directory is done with the git checkout command.
So, you've got this conceptually? Working directory, repository, staging area? Right. This is what you should work with.
I got very confused by how this is actually built. The repository and the staging area are stored in a folder called .git which is contained within the working directory.
This made my head wobble. Surely, not inside the directory? Surely, that way lies folly? Infinite recursions? Surely it should be external? But that's how it's built. Inside. It's elegant once you start thinking about it but it made my head hurt.
Start with the command line
I would recommend staring with a command-line interface. I know that there are many GUI Interfaces out there (SourceTree being a particularly good one), but all they are doing is adding an interface on top of the command-line instructions.
I would recommend moving to a GUI once you've learnt the basics of git. Additionally, the command line is very helpful for noobs, as it notices when you have typed something that doesn't make sense and makes a suggestion. Stackoverflow and the git documentation are the place to go if you get stuck.
http://gitref.org/ is a good, compact resource.
You can download the git command-line bash here.
Recommended Reading
This is a tip from Eric McCormick.
Useful Commands
Here I have listed those commands which I am using regularly and feel comfortable with:
[code gutter="false"]
git init
First initialization, creates the magical hidden folder .git. This is where the actual repository is stored (see above). You'll need to select the directory which you want to 'track'
Staging means 'saying these are the files I wish to commit'
The command for staging is
[code gutter="false"]
git add <filename>
alternatively you can use
[code gutter="false"]
git add .
which will add all the files in the current directory (. is the current directory)
[code gutter="false"]
git commit –message='Committing message'
The convention is to write a message with multiple lines, a bit structured like an e-mail. The first line should be like the subject of the e-mail, the other lines are the 'body' of the e-mail.
Creating a remote repository:
[code gutter="false"]
git remote
shows the remote repository linked to the current repository. You'll need to have created this beforehand on the github site.
I use github, so the example here is with github. First log into GitHub and create a repository there. Note the URL of the remote repository (there is a convenient button for this)
[code gutter="false"]
git remote add origin <your remote repository URL>;
Note: origin here is one of these conventions, it's the default name of the remote repository. Don't make the mistake of naming one of your remote branches origin. Remember, convention!
[code gutter="false"]
git remote -v
shows the urls linked to your remote repository.
[code gutter="false"]
git remote show origin
This command shows all the branches on the origin repository (the remote one, origin is its name by default)
[code gutter="false"]
git fetch
fetches the data from the external repository but does not merge the data.
[code gutter="false"]
git pull
fetches, then merges the data.
[code gutter="false"]
git push <remote> <local branch name>:<remote branch to push into>
pushes the data from the local repository to the remote one.
Checkout (restore files or change branch)
[code gutter="false"]
git checkout
This switches branches or restores working tree files. It's a bit of an uncomfortable command at first because it seems to be doing two completely different things. Actually, it's doing the exact same thing – it's overwriting your working directory with information from a particular commit. Your working directory is a scrapbook, remember?
I find this useful to avoid committing fluff (my technical term for files which have, technically, changed (a timestamp for instance) but which are not actually changes.) I add the files that I want to have committed with gid add, then I do a git commit, and then a
[code gutter="false"]
git checkout — .
to overwrite the fluff in the working directory.
If you notice you've just committed nonsense (in this example I replaced the whole About This Database with nothing), you want to restore the file to what it was before. Here comes git checkout for helping again:
[code gutter="false"]
git checkout HEAD~1 — odp/Resources/AboutDocument
HEAD~1 is a way to refer to a specific commit, i.e. 'The commit on HEAD' minus (~) one (1)
Conventions for naming files and directories:
dash dash
If you see — before a filename, it's a disambiguator saying 'what follows are necessarily files'
. is the current directory – so, everything.
Syntax for defining an entire directory with everything in it
odp/Resources/ would define that particular directory, along with anything inside it. Note the trailing slash!
Conventions for naming commits:
Naming conventions:
HEAD: Head is a pointer the commit that was pushed into the working directory last. Think of it as 'commit corresponding to the current state of my working directory before I made any changes'.
<commit name>~1 The tilde here means 'minus', so this would be the previous commit.
Configuration options that are useful
In git Bash, I immediately increase the font size to something readable with our big screens, and then
[code gutter="false"]
git config –global core.autocrlf false
which avoids the annoying 'lf/crlf' comments, since I'm mostly working in a windows environment (sniff).
Do this before your initial commit! (see https://help.github.com/articles/dealing-with-line-endings/)
Setting up SSH keys with Git Bash
Since I'm lazy and don't want to type in password and username every time I connect to git, here's how to do it it cleanly via ssh.
[code gutter="false"]
ssh-keygen -t rsa -b 4096 -C "email@example.com"
Press Enter for default in which to save key enter a passphrase (a complicated one, alright?)
Add the keys to the ssh-agent (This is a background agent whose job is to always automatically enter your passphrase in. You should be aware that this makes your local physical machine a lot more vulnerable)
[code gutter="false"]
eval $(ssh-agent -s)
ssh-add ~/.ssh/id_rsa
copy the PUBLIC key to the clipboard (windows)
[code gutter="false"]
clip < ~/.ssh/id_rsa.pub
or mac OS
[code gutter="false"]
pbcopy < ~/.ssh/id_rsa.pub
add the ssh key to your github account Test the keys with
[code gutter="false"]
ssh -T firstname.lastname@example.com
Ignoring certain files or directories
There are some occasions when you don't want certain files to be tracked by git. Typically, there are for instance binaries of your source code, or hidden files generated by your ide.
You can see which files are not being tracked with this command:
[code gutter="false"]
git ls-files –others –exclude-standard
or alternatively,
[code gutter="false"]
git add -A -n
There are unfortunately many different ways to define the excluded files. There is a central configuration file, whose location one can find with
[code gutter="false"]
git config –get core.excludesfile
Within your project, there are two files that control the exclusions:
[code gutter="false"]
Confused? Here is an explanation from Junio Hamano (the maintainer of Git)
The .gitignore and .git/info/exclude are the two UIs to invoke the same mechanism. In-tree .gitignore are to be shared among project members (i.e. everybody working on the project should consider the paths that match the ignore pattern in there as cruft). On the other hand, .git/info/exclude is meant for personal ignore patterns (i.e. you, while working on the project, consider them as cruft).
This command combination is practical (thanks Akira Yamammoto)
[code gutter="false"]
git rm -r –cached .
(recursively remove all the cached files (i.e. tracked) from the current directory) then
[code gutter="false"]
git add .
git commit -m "fixed untracked files"
Notes/Domino best practices
Best practice when gitting an odp project: Never disconnect the nsf from the eclipse project.
Never change the nsf the odp is connected to.
Thanks to Adrian Osterwalder for the tips.