git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Howto request: going home in the middle of something?

From
Petr Baudis <pasky@suse.cz>
Date
Oct 18, 2007, 11:27 UTC
Message-ID
<20071018112758.GN18279@machine.or.cz>
In-Reply-To
<200710181144.22655.wielemak@science.uva.nl>
  Hi,
On Thu, Oct 18, 2007 at 11:44:22AM +0200, Jan Wielemaker wrote:
Show 14 quoted lines
> I've somewhere seen it in a mail, but I can't find it anymore. I have a
> bare central (public) repository and clones on various machines I work
> on. We all know it, you're right in the middle of something and it is
> really time to go home. You want to pick up your work at home, but
> without pushing to the shared repository.
> 
> I'm sure GIT can do this elegantly, but I'm not yet sure how.  I guess
> Ideally I want "git stash" at work, transfer the stashed changes to my
> other machine and apply them.  How do I do that?
> 
> Alternatively, I guess, one can commit at machine A, fetch the commit
> from machine A and continue. I'm still too uncertain about the remote
> access options to work this out properly, but it also feels less
> clean.
  this should be pretty simple assuming SSH access to machine A. Git can
fetch over SSH, so it's merely about telling it that repository X is
available over ssh over there and it'll fetch it home.
  The exact setup depends on whether you want to do this just once or
semi-regularily.  If the former, just
	git pull git+ssh://a.machine.aero/absolute/path

Note that this should fetch only the remote master branch, if I'm not mistaken.

  If the latter, tell your home repository about your work repository:
	git remote add workrepo git+ssh://a.machine.aero/absolute/path
  Then, you can anytime just
	git fetch workrepo

and it will fetch all the branches from workrepo; whether you want to use git fetch and git merge or git pull depends on your local arrangement of branches at home.

  So, basically, when fetching you deal with your work repository
exactly the same way as in the shared repository.
  When pushing, this is not so trivial. Git _allows_ you to just push to
your work repository, but if you push to a branch that is currently
checked out, unexpected things will happen - always avoid that. If you
can fetch from home at work, do. If not, at least push to a branch at
work that can never be checked out and is reserved for that purpose.
-- 
				Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
                -- James Thurber
Previous: Karl HasselströmNext: Jan Wielemaker
Message 4 of 11 in “Howto request: going home in the middle of something?”
  1. Jan WielemakerOct 18, 2007
  2. Johannes SixtOct 18, 2007
  3. Karl HasselströmOct 18, 2007
  4. Petr BaudisOct 18, 2007
  5. Jan WielemakerOct 22, 2007
  6. Johannes SchindelinOct 22, 2007
  7. Jing XueOct 23, 2007
  8. Jan WielemakerOct 23, 2007
  9. Matthias KestenholzOct 23, 2007
  10. Jing XueOct 24, 2007
  11. Andy ParkinsOct 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.