From: Stefan F. <ste...@we...> - 2012-10-09 12:31:59
|
Erik: were you able to proceed? I am using git push origin rails2.0 to push only rails2.0 and git push origin to push all. What Brett is suggesting is to define an alias command: e.g. git-config alias.pushAll push origin git-config alias.pushTwo push origin rails2.0 My experience with pushing is that is harder to get the push done, instead of pushing bad things. And even if you, it is easy to fix, just complain and either Brett or I will step in. I did a few hundreds of cherry-picks with conflicts already and had not one bad experience so far with git. Even if everything gets messed up it is easy to redo (or to fix with rebase --interactive). Stefan On 10/06/2012 07:58 PM, Erik Vos wrote: >>> remote.origin.push=refs/heads/master:refs/heads/master >> >> This line isn't needed. A better way (imo) would be to set an alias. >> >> But it's also functionally equivalent to "git push origin master" > > I don't trust myself remembering that every time. > > What I want is to have 'git push' upload just the one (maybe two) branch(es) > with which I work, or into which I merge my local branches. > All my own local branches that do not exist in the remote repo should be > excluded from uploading. > I want just the simple 'git push' do that, as it does now, because the > current configuration makes me push 'master' only. > > How can I set that up without 'remote.origin.push'? > > Erik. > > > > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |