From: Eric Bowman <ebowman@boboco.ie>
To: git@vger.kernel.org
Subject: newbie question about git push
Date: Wed, 27 Aug 2008 17:37:20 +0200 [thread overview]
Message-ID: <48B574B0.4030607@boboco.ie> (raw)
Hi,
Apologies in advance if this has been covered before ... I've been
wading through the archives a bit and couldn't find anything that seemed
to address this basic question.
I have a bunch of machines I use for development, but only one of them
is allowed to connect via vpn to where the subversion repository lives,
so I'm using git-svn to make things a little easier.
I've got one machine, itchy, where I've done a git svn clone operation.
I do a fair amount of development work there, and typically I just work
on the master branch, and periodically commit back to svn using git svn
dcommit.
I've cloned the repository on itchy on a few other machines I
occasionally use, and I'm able to push new revisions from itchy with no
surprises, and I can pull revisions back to itchy ok with no surprises.
Where things get a weird is when I push a revision back to itchy from
one of my other clones. I feel like I must be missing some fundamental
concept, and I'm wondering if someone can help.
Suppose I make a change on another machine commit that change, then push
it back to itchy:
git commit -as
git push origin master
This works ok, and I can then git svn dcommit that change back to the
svn. But I have a hard time getting that change to show up in the
sandbox I have on itchy.
When I go back to itchy after pushing from a satellite, git thinks that
the old revision of the file I modified on another machine, has been
modified locally; it doesn't see that the local copy is out of data and
this new revision needs to be merged. But I can't figure out how to get
git to do that; the only things that seem to work are fairly drastic
measures, like "git reset --hard" or by stashing and then deleting the
stash. Either seems terribly error prone.
I'm starting to think that I should clone the repo I cloned from svn for
doing development work on itchy, but this seems kind of wasteful. Am I
missing some fundamental concept?
Many thanks for any thoughts.
cheers,
Eric
next reply other threads:[~2008-08-27 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 15:37 Eric Bowman [this message]
2008-08-27 15:52 ` newbie question about git push Peter Harris
2008-08-27 16:06 ` Michael J Gruber
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=48B574B0.4030607@boboco.ie \
--to=ebowman@boboco.ie \
--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 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.