I have a library and several small programs that use it: how should I structure my git repositories?

I have some code that uses a library that I and others frequently modify (usually only by adding functions and methods). We each keep a local fork of the library for our own use.

Why not commit unresolved changes?

In a traditional VCS, I can understand why you would not commit unresolved files because you could break the build. However, I don’t understand why you shouldn’t commit unresolved files in a DVCS (some of them will actually prevent you from committing the files).

VCS for single user using file sync service [closed]

Closed 10 years ago.

What’s the best way to manage reusable classes/libraries separately?

When coding, I naturally often come up with classes or a set of classes with a high reusability. I’m looking for an easy, straight-forward way to work on them separately.
I’d like to be able to easily integrate them into any project; it also should be possible to switch to a different version with as few commands as possible.

Bulk commits vs Quick commits [closed]

It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I know that most of you would advice […]

Dropbox as a Version Control tool [closed]

It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I have some friends telling me that Dropbox […]

Conceptual difference between Git and GitHub

The last line of this answer prompted me to ask this question . I know to know at a conceptual level the difference between Git and GitHub .

Bump version before kicking off new development or when tagging a release, which is better?

Some projects bump version before kicking off a new development, while the other projects bump version when tagging a release.

Why are source control systems still mostly backed with files?

It seems that more source control systems still use files as the means of storing the version data. Vault and TFS use Sql Server as their data store, which I would think would be better for data consistency as well as speed.

How do professional application developers use version control systems, like GIT and Subversion?

I am a beginner developer and I have been wondering from the start, how do professional use tools like GIT and Subversion (I don’t have a very good understanding about these tools), to fulfill their project’s needs. If they do use it, how would I set up something like that?