From: Jing Xue <jingxue@digizenstudio.com>
To: Matthias Kestenholz <mk@spinlock.ch>
Cc: Jan Wielemaker <wielemak@science.uva.nl>,
Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org
Subject: Re: Howto request: going home in the middle of something?
Date: Wed, 24 Oct 2007 09:44:14 -0400 [thread overview]
Message-ID: <20071024134414.GA15710@falcon.digizenstudio.com> (raw)
In-Reply-To: <256C87B5-3ADE-4A96-9530-A45B97601BAA@spinlock.ch>
On Tue, Oct 23, 2007 at 10:28:46PM +0200, Matthias Kestenholz wrote:
> Hi,
Hi,
> If someone tracks the main branch you are working on and fetches
> while you are travelling home, he has the WIP commit as a new tip
> in his tree.
> If he bases further work upon the WIP commit, he'll need to rebase
> or merge his changes onto your new tip once you have amended or
> replaced the commit. If you are working on the
> master branch, you should really avoid rewinding it. Rewinding topic
> branches is ok, but a temporary branch is still better to clearly tell
> potential fetch-ers that this is only Work in Progress, and not meant
> to be published in the current state.
Good point. Although I guess if some workflow lets you directly hack on a
public branch, it can have lots of other issues beyond just the WIP
being pulled accidentally, no?
Cheers.
--
Jing Xue
next prev parent reply other threads:[~2007-10-24 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 9:44 Howto request: going home in the middle of something? Jan Wielemaker
2007-10-18 10:37 ` Johannes Sixt
2007-10-18 11:07 ` Karl Hasselström
2007-10-18 11:27 ` Petr Baudis
2007-10-22 8:44 ` Jan Wielemaker
2007-10-22 11:32 ` Johannes Schindelin
2007-10-23 17:56 ` Jing Xue
2007-10-23 18:38 ` Jan Wielemaker
2007-10-23 20:28 ` Matthias Kestenholz
2007-10-24 13:44 ` Jing Xue [this message]
2007-10-18 11:29 ` Andy Parkins
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=20071024134414.GA15710@falcon.digizenstudio.com \
--to=jingxue@digizenstudio.com \
--cc=git@vger.kernel.org \
--cc=mk@spinlock.ch \
--cc=pasky@suse.cz \
--cc=wielemak@science.uva.nl \
/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).