From: g2 <gerald.gutierrez@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: How to jump between two repositories ...
Date: Wed, 5 Dec 2007 07:28:02 -0800 [thread overview]
Message-ID: <9F403ACE-62C0-4A6D-945C-3DA6DF0316B8@gmail.com> (raw)
In-Reply-To: <47566526.9010900@op5.se>
How do you safely push to the repository? Even if my receiving
repository is pristine (the last command I do is a commit), after I
push into it, some files in the work-tree are effectively out of date
and git says so by thinking they are modified and staged for commit.
My original set of example commands illustrates this. What set of
commands do you use to avoid the problem?
On 5-Dec-07, at 12:45 AM, Andreas Ericsson wrote:
>
> Yes it does. It just supports it badly. If there is a work-tree
> connected to
> the receiving repository and that work-tree is pristine, it would be
> safe and
> sane to write the newly pushed changes to the connected working tree.
>
> We do all our integration fixups by pushing to repositories with
> work-trees,
> simply because it's ridiculously inconvenient to add the
> infrastructure to
> pull to those repos from each individual developer. In that
> scenario, pushing
> to a checked out branch is highly useful and perfectly safe.
>
> --
> Andreas Ericsson andreas.ericsson@op5.se
> OP5 AB www.op5.se
> Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-12-05 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 5:59 How to jump between two repositories g2
2007-12-05 6:11 ` Shawn O. Pearce
2007-12-05 6:14 ` J. Bruce Fields
2007-12-05 8:45 ` Andreas Ericsson
2007-12-05 15:28 ` g2 [this message]
2007-12-05 16:19 ` Andreas Ericsson
2007-12-05 6:20 ` Väinö Järvelä
2007-12-05 6:44 ` g2
2007-12-05 6:57 ` Steven Grimm
2007-12-05 7:32 ` Väinö Järvelä
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=9F403ACE-62C0-4A6D-945C-3DA6DF0316B8@gmail.com \
--to=gerald.gutierrez@gmail.com \
--cc=ae@op5.se \
--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;
as well as URLs for NNTP newsgroup(s).