From: Dmitry Smirnov <divis1969@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git drawbacks?
Date: Tue, 10 Nov 2009 09:08:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20091110T100345-116@post.gmane.org> (raw)
In-Reply-To: 28c656e20911091047r353e9451hd856b99541fbd5ff@mail.gmail.com
B Smith-Mannschott <bsmith.occs <at> gmail.com> writes:
> You don't have to wait to comitting to your own branches, but do make
> sure to run your usual builds and tests before pushing or asking
> another to pull changes from you.
Perhaps, I was not clear in my questions.
I do not want to build and test to complete before I get back to my stashed
or commited changes. I.e. I need to have 2 working trees (perhaps different, but
from the same repository): one for build/test and one for another task.
Dmitry
next prev parent reply other threads:[~2009-11-10 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:17 Git drawbacks? Dmitry Smirnov
2009-11-06 16:49 ` Avery Pennarun
2009-11-06 17:35 ` Dmitry Smirnov
2009-11-06 17:41 ` Jacob Helwig
2009-11-06 17:51 ` Avery Pennarun
2009-11-06 18:57 ` david
2009-11-09 7:53 ` Dmitry Smirnov
2009-11-09 14:34 ` Jacob Helwig
2009-11-09 15:59 ` Dmitry Smirnov
2009-11-09 16:21 ` Jacob Helwig
2009-11-09 15:48 ` Dmitry Potapov
2009-11-09 16:11 ` Dmitry Smirnov
2009-11-09 18:34 ` Dmitry Potapov
2009-11-10 8:31 ` Dmitry Smirnov
2009-11-10 13:45 ` Dmitry Potapov
2009-11-10 14:14 ` Dmitry Smirnov
2009-11-10 16:15 ` Paolo Bonzini
2009-11-09 18:47 ` B Smith-Mannschott
2009-11-09 21:06 ` Dmitry Potapov
2009-11-10 8:51 ` Dmitry Smirnov
2009-11-10 14:04 ` Dmitry Potapov
2009-11-10 14:54 ` Dmitry Smirnov
2009-11-10 16:20 ` Paolo Bonzini
2009-11-10 23:43 ` Dmitry Potapov
2009-11-10 9:08 ` Dmitry Smirnov [this message]
2009-11-09 7:22 ` Dmitry Smirnov
2009-11-11 10:21 ` Dmitry Smirnov
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=loom.20091110T100345-116@post.gmane.org \
--to=divis1969@gmail.com \
--cc=git@vger.kernel.org \
/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