On Jun 11, 2008, at 12:52 PM, David Reiss wrote:
There's really no need to use a central repository for git users,
IMO,
people should be free to choose their own publishing point. There is
not much difference in:
git pull . pri/<somebody>/<branch> // which is equivalent to git
merge
pri/<somebody>/<branch>
and
git pull <somebodys_remote> <branch>
where <somebodys_remote> can be either be the full Git url or
configured by: git remote add <remote> <url>
I wouldn't mind a backup in the pri/... branches though.
I strongly disagree. A single central repository that contains
everyone's branches means that you only have to go to one place (the
Gitweb heads page, which is sorted by last update time) to see
everything that is going on in Git land. If everyone hosts their own
repository, it significantly increases the effort required to track
current developments.
I can see someone who wants the sense of being on top of things
wanting that :) That's fine, though, a git user can have multiple
remotes trivially. It's just easier to be able to do git push origin
<branch> instead of git push thrift pri/<user>/<branch>. A central
repository like this just encourage people to publish less to this
remote, which might not be a bad thing (one thing I learned in git is:
when in doubt, commit and you can always rebase -i to split/squash/
reorder/amend later, and use remotes as backup mechanism, which can
cause a lot churns in private branches)
Honestly, I don't see any difference in terms of effort of tracking
things when a contributor can post their url on Jira, people can just
click it to see what's up.
This needs to be well documented. Also, will non-Git users need to
consult this "one place"?
I think non-git users should just stick to the subversion
respository,
which should be the "official" repository for the Apache project. The
official branches (trunk and releases) needs to be sync'ed (with git-
svn) regularly using a post-commit hook in the "semi-official" git
repository, which is the merge point of Git users.
I disagree with this also. I want non-Git users to be able to comment
on branches that I submit for review.
I think I'm misunderstood. Nothing prevent a non-git user to click on
a url posted on Jira or the mailing list to see the change and make
comments. They can even send vanilla patches. If they're git users,
things are just a little easier.
Also, we will not be publishing
changes from Git back into SVN automatically at any time in the
foreseeable future.
I think there is a merit syncing master/trunk and release changes. So
casual SVN "users" can check out the latest "official" code and play/
test with it.
__Luke
