versioning

Today I discovered a bug for Git on Mac OS X. For example, I will commit a file with the name überschrift.txt with the German special character Ü at the beginning. From the command git status I get following output. Users-iMac: user$ git status On branch master # Untracked files: # (use "git add <file>..." to include in what will be committed) # # "U\314\210berschrift.txt" nothing added to commit but untracked files present (use "git add" to track) It seems that Git 1.7.2 has a problem with German special characters on Mac OS X. Is there a solution to get Git read the file names correct? Leo

I want to add a "Check for update" button in apps so that when someone clicks it, it will display a toast message / progress dialog for checking the app's version. If new version is found the apps will auto download it to the phone and let user to manually install the updated apps. Or any others method will do as long as it can check for latest version and notify the user to update. Google updated play store two months before. This is the solution working right now for me.. class GetVersionCode extends AsyncTask<Void, String, String> { @Override protected String doInBackground(Void... voids) {

I've been searching how to manage a REST API versions using Spring 3.2.x, but I haven't find anything that is easy to maintain. I'll explain first the problem I have, and then a solution... but I do wonder if I'm re-inventing the wheel here. I want to manage the version based on the Accept header, and for example if a request has the Accept header application/vnd.company.app-1.1+json , I want spring MVC to forward this to the method that handles this version. And since not all methods in an API change in the same release, I don't want to go to each of my controllers and change anything for a

We have a requirement in project to store all the revisions(Change History) for the entities in the database. Currently we have 2 designed proposals for this: e.g. for "Employee" Entity Design 1: -- Holds Employee Entity "Employees (EmployeeId, FirstName, LastName, DepartmentId, .., ..)" -- Holds the Employee Revisions in Xml. The RevisionXML will contain -- all data of that particular EmployeeId "EmployeeHistories (EmployeeId, DateModified, RevisionXML)" Design 2: -- Holds Employee Entity "Employees (EmployeeId, FirstName, LastName, DepartmentId, .., ..)" -- In this approach we have basically

As part of our build process I need to set the version information for all of our compiled binaries. Some of the binaries already have version information (added at compile time) and some do not. I want to be able to apply the following information: Company Name Copyright Notice Product Name Product Description File Version Product Version All of these attributes are specified by the build script and must be applied after compilation. These are standard binaries (not assemblies) compiled with C++ Builder 2007. How can I do this? While it's not a batch process, Visual Studio can also add/edit

What is the best way to version REST URIs? Currently we have a version # in the URI itself, ie. http://example.com/users/v4/1234/ for version 4 of this representation. Does the version belong in the queryString? ie. http://example.com/users/1234?version=4 Or is versioning best accomplished another way? I would say making it part of the URI itself (option 1) is best because v4 identifies a different resource than v3. Query parameters like in your second option can be best used to pass-in additional (query) info related to the request , rather than the resource . Darrel Miller Do not version