From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jing Xue <jingxue@digizenstudio.com>, Patrick Doyle <wpdster@gmail.com>
Subject: Re: yet another workflow question...
Date: Fri, 12 Oct 2007 08:25:57 +0100 [thread overview]
Message-ID: <200710120825.58235.andyparkins@gmail.com> (raw)
In-Reply-To: <20071011164019.3n4l3rayckck8c4w@intranet.digizenstudio.com>
On Thursday 2007 October 11, Jing Xue wrote:
> Quoting Andy Parkins <andyparkins@gmail.com>:
> > - Mobility. This one is a bit distributed, but I hope you'll let
> > me have it.
> > I often do work on my desktop at home, my desktop at work and my
> > laptop. By setting my remotes up correctly in git it's really easy to
> > walk to another system and pick up exactly where I left off from the
> > other computer. More importantly though, when you accidentally make
> > changes in two places, there is no danger of data loss.
>
> To extend on this point, after picking up the randomly checked-in save
> point on another computer, the save point itself can be easily
> git-reset'ed. So there won't be commits like "it's utter broken but i
> got to go home" polluting the history. I find that extremely handy.
Absolutely; in fact I've had times when I've done things like this:
git merge laptop-branch
git merge home-branch
git reset HEAD^^
That is to say, I'm not interested in documenting the merges, I just want to
bring a set of changes from different places together ready for some proper
commits, which of course can be done really easily with git add -i.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
prev parent reply other threads:[~2007-10-12 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 14:11 yet another workflow question Patrick Doyle
2007-10-11 14:18 ` David Kastrup
2007-10-11 14:44 ` Steffen Prohaska
2007-10-11 14:37 ` Johannes Sixt
2007-10-11 14:39 ` Wincent Colaiuta
2007-10-11 15:10 ` Andy Parkins
2007-10-11 17:28 ` Andreas Ericsson
2007-10-11 20:40 ` Jing Xue
2007-10-12 7:25 ` Andy Parkins [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=200710120825.58235.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jingxue@digizenstudio.com \
--cc=wpdster@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.