Re: RFC: git sync
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Feb 10, 2010, 09:52 UTC
- Message-ID
- <m3wryl8lkp.fsf@localhost.localdomain>
- In-Reply-To
- <20100210032720.GA5205@cthulhu>
Larry D'Anna <larry@elder-gods.org> writes:
Show 16 quoted lines
> So say you have a project with a bunch of branches. You have two main computers > you work on: a laptop and a workstation, and you keep an authoritative copy on a > server somewhere. When you sit down at your laptop to work on your project, the > first thing you want to do is make sure that whatever you've got locally is > up-to-date with the repo on the server. So you run: > > git push origin : > > Then if it says anything isn't a fast-forward, you use some combination of git > pull, git checkout, or git fetch to get all you branches up to date, then > possibly you run the push again to push merges back to the server. > > How about instead we add a new command called "git sync" that does all that for > you? So if you say > > git sync origin :
[...]
> What do you all think? If you like the idea, I'll do it as a builtin. > Otherwise I'll just hack up a perl script for myself.
Why not use the recpie from GitFaq: "How would I use "git push" to sync out of a host that I cannot pull from?" http://git.wiki.kernel.org/index.php/GitFaq#How_would_I_use_.22git_push.22_to_sync_out_of_a_host_that_I_cannot_pull_from.3F
-- Jakub Narebski Poland ShadeHawk on #git