From: Tobiah <toby@tobiah.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Working from different machines.
Date: Thu, 18 Aug 2016 07:11:51 -0700 [thread overview]
Message-ID: <c374f742-bc42-fdb5-37e8-f795a14259a2@tobiah.org> (raw)
In-Reply-To: <xmqq4m6j81ci.fsf@gitster.mtv.corp.google.com>
On 08/17/2016 03:41 PM, Junio C Hamano wrote:
> Tobiah <toby@tobiah.org> writes:
>
>> In other words, I want to work from different machines, and always
>> sit down to the environment exactly as I last left it.
>
> You have several options, but it depends on untold expectations you
> have beyond "exactly as I last left it." So the following is only
> to show directions and possibilities without going into details.
>
> For example, do you save all changes you made in your editor buffers
> before you leave the 'desktop'? If the answer is "no", then that is
> not a problem Git-the-tool is interested in solving, and the only
> solution I could think of is to use mechanism to share the session
> between 'desktop' and 'home', using things like remote-desktop or
> screen session.
>
> If the answer is "yes", the next question is if you commit all the
> changes you made before you leave the 'desktop'. If the answer is
> "no", again, that is not a problem Git-the-tool is interested in
> solving, and the only solution I could think of (in addition to the
> "share the session" above) is to use networked filesystem shared
> between 'desktop' and 'home'.
>
> If the answer is "yes", then you are in the problem space that
> Git-the-tool is interested in solving. Assuming that you have
> network connection into 'desktop' from 'home', the solution would
> involve making it the first thing to do when get home to run "git
> fetch" on 'home' to get the latest state from the 'desktop', and run
> "git push" on 'home' to push out the latest state to the 'desktop'
> before you leave 'home'. If your 'server' is for your sole use, and
> if 'home' has network connection into 'server', then you could
> instead rendezvous at 'server' by running "git push server" on
> 'desktop' (or 'home') to 'server' as the last thing before you leave
> 'desktop' (or 'home'), and running "git fetch server" on 'home' (or
> 'desktop') as the first thing before you start working on 'home' (or
> 'desktop').
>
I've done a poor job of expressing my need. I'm only
speaking about the state of each git project directory.
Shared sessions or filesystems are not what I'm loolking
for.
As far as the master branch goes, I have no problem syncing
everything to the server, then pulling to a different
machine. When I said I want everything to be the same
between the home and work machines, I meant with regard to
all of the other branches. I want to easily create an
entire movable git environment that is indistinguishable
from machine to machine.
It looks like --mirror is close to what I am looking for.
Thanks
prev parent reply other threads:[~2016-08-18 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 21:47 Working from different machines Tobiah
2016-08-17 22:41 ` Junio C Hamano
2016-08-18 6:10 ` Jacob Keller
2016-08-18 12:29 ` Jakub Narębski
2016-08-18 14:28 ` Tobiah
2016-08-18 16:53 ` Jakub Narębski
2016-08-18 14:11 ` Tobiah [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c374f742-bc42-fdb5-37e8-f795a14259a2@tobiah.org \
--to=toby@tobiah.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).