repository

We're starting a new project in Python with a few proprietary algorithms and sensitive bits of logic that we'd like to keep private. We also will have a few outsiders (select members of the public) working on the code. We cannot grant the outsiders access to the small, private bits of code, but we'd like a public version to work well enough for them. Say that our project, Foo, has a module, bar , with one function, get_sauce() . What really happens in get_sauce() is secret, but we want a public version of get_sauce() to return an acceptable, albeit incorrect, result. We also run our own

I'm working on a project with several corporate remote Maven repositories, each hosting many dozens of dependencies. The entire project uses hundreds of dependencies and I need a way to quickly determine which remote repository a dependency is stored on . Does Maven provide an easy way to do this or do I need to search through each repository's dependency listing myself? The project dependencies report has the information you want. You can quickly generate just this report using mvn project-info-reports:dependencies and open the target/site/dependencies.html file. Look at the last section in

I know about Fossil but are there any alternatives? Something small and easy to install/configure. I know there are quite a few git-based wikis such as git-wiki , WiGit and gitit . A simple google search will bring up many others, I'm sure. I also know of some git-based bug trackers such as ticgit which basically lets you keep your tickets in a separate branch of a git repository. There's also DisTract . But I'm not aware of anything else aside from Fossil that really tries to do what it does in one combined tool. I'm curious what your experiences with Fossil have been. It's one of those

Skip to the "specific question" as needed. Some background: The scenario: I have a set of products with a "drill down" filter (Query Object) populated with DDLs. Each progressive DDL selection will further limit the product list as well as what options are left for the DDLs. For example, selecting a hammer out of tools limits the Product Sizes to only show hammer sizes. Current setup: I created a query object, sent it to a repository, and fed each option to a SQL "table valued function" where null values represent "get all products". I consider this a good effort, but far from DDD acceptable.

I have two small git repos. The projects both started from different points but converged to a very similar one (same file names, folder structure, etc). One is not a branch of the other, but one can be considered an evolution of the other. It would be nice if I could merge the two so that repo2 is the continuation of repo1 . Is this possible, whilst adding the history of repo2 to the end of repo1 's? VonC You can fetch one into another : $ cd project1 $ git config remote.project2.url /path/to/project2 $ git config remote.project2.fetch 'refs/heads/*:refs/project2/*' $ git fetch project That

The only documentation about googles 'repo' tool for android repository management was: https://sites.google.com/a/android.com/opensource/download/using-repo This was less than nothing: the available help is the same as when typing: repo help Does anyone know another source of documentation? I explicitly want to know how to revert local changes: -of a git repository that is part of the 'repo' -of the repo '/manifest' folder or other 'repo' changes Documentation about repo is a bit hard to come about, as you have discovered. In addition to your link, the repo help <subject> commands are very

I have a central repository with a subset of files that I want to protect from being changed (by pushing) from other users. If I add these files to .gitignore , they would not be cloned. Is it possible to give the ability to clone all files, but after cloning add some of them to .gitignore on the client side? You can have the files in the repository, commit them, then add them to the .gitignore and then remove them from the next commit. You can still fetch the files directly prior commit (perhaps tag it with something so it can be fetched by name a bit easier) and this will preserve the state

I'd like to make my application as flexible as possible, but not dig myself into a hole by making my Interface too specific. What is the best object type for a repository? IEnumerable, IQueryable, or List? The technologies I'm considering using are Azure App Fabric Caching Entity Framework 4.1 Possibly Windows Server AppFabric I would say build your DAL using IQueryable, and pass it around, make sure your object contects lifetime is the request. This way you will get benefit of delayed execution, but are exposed to the risk of inefficient querying of database. Then make sure you performance