Re: Pushing everything

From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Date: Oct 31, 2010, 12:30 UTC
Message-ID: <20101031123031.GE18845@localhost.localdomain>
In-Reply-To: <loom.20101031T064406-734@post.gmane.org>

On Sun, Oct 31, 2010 at 05:47:38AM +0000, Maaartin wrote:

Show 18 quoted lines

> I'd like to push all my branches and tags to the server, but for whatever reason 
> "--all" ignores tags and is incompatible with "--tags". I could imagine there's 
> a reason I'm not experienced enough to see?
> 
> It seems to me that "--mirror" is quite unusable, since it force-overwrites the 
> remote repo and even deletes refs not locally present. Obviously, a mirror can't 
> be shared, and it doesn't seem to me to be the ideal backup solution for a 
> single person.
> 
> However, even if "git push -all -tags"  worked, I'm not sure it's a good idea 
> for project with more collaborators. There may be conflicts or other problems 
> and quite often the pushing occurs just before leaving so it's no good time to 
> start resolving conflicts. Can a shared repo be used as a sort of backup as 
> well? I'd like a possibility to backup all my work there anytime without needing 
> to care about anything. This could work by creating sort of private refs in case 
> of any problems, or whatever. Is there something like this, or am I thinking 
> astray? I'd suppose, something like this could be very useful for a company 
> where it'd provide a simple backup solution for everybody.

You can have any number of remotes configured for your local repo. So you can easily have one "private" remote repo which you use solely for "backup" pushes and one "shared" remote repo to which you do careful selective pushes.

Note that I'm obsessed with the "backup" idea no less than you and when I started using Git I learned about --mirror and did mirror push to my private remote repo before leaving office, just as you explained. But then I realized this was just a hangover from my Subversion backgrounds, and that to really need --mirror doing regular programming, you have to be fantastically, inhumanly productive. I mean, after a typical one work day programming session you usually have a clear idea about what branch(es) and what tags, if any, you have to push for backup purposes. So it really might be a non-issue.