On 4/19/07, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote:
2. There's no easy way to tell that you've made commits that you haven't
pushed upstream. In fact, it's impossible to tell when disconnected
whether you've pushed everything. This needs some command to report it,
and also for push to update the fetch sides of remote heads it updates.
Cogito does this (push updating the refs), and I like it. I think it's
worth doing. Then git-branch -v could flag pending-to-push local
branches.
3. You can't create a new repository by pushing, even if you could
actually create the repository. Obviously, this will be blocked by
policy more often than pushing in general would be, but it's not
always blocked. It's also harder than it should be to turn a repository
created locally into a repository identical in configuration to a clone
of a newly-created remote repository.
It's not too hard to do a
git-publish git+ssh://host/path/to/repo.git
that just does a git init or maybe rsyncs out.
4. Creating new branches off of existing branches/remotes doesn't
configure the new branches in the obvious way (i.e., such that the
default update action matches the create action).
Junio was pointing out recently that there's an option for that -
pull.automerge I think - that you can set in your /etc/gitconfig. Or
you can say --track
cheers,
martin
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html