From: Michael J Gruber <git@drmicha.warpmail.net>
To: michael.meeks@novell.com
Cc: git@vger.kernel.org, kendy@novell.com,
Norbert Thiebaud <nthiebaud@gmail.com>
Subject: Re: libreoffice merge(tool?) issue #3 ...
Date: Tue, 22 Feb 2011 18:30:45 +0100 [thread overview]
Message-ID: <4D63F2C5.2080505@drmicha.warpmail.net> (raw)
In-Reply-To: <1298388877.32648.171.camel@lenovo-w500>
Michael Meeks venit, vidit, dixit 22.02.2011 16:34:
> Hi there,
>
> So - yet again, I'm still a completely clueless git user :-)
> basically the same setup and reproduction issue as last time, still
> using a stable git: version 1.7.3.4
<PG>
I'm sorry you're having reproduction issues. At least your git is stable.
</PG>
>
> Setup:
> git clone git://anongit.freedesktop.org/libreoffice/libs-core
cd libs-core # I assume
> git checkout integration/dev300_m98
> git remote add stage git://anongit.freedesktop.org/libreoffice/staging/libs-core
> git fetch stage
>
> Reproduce:
> rm -Rf *
> git reset --hard # ie. totally clean tree.
# Those two should be no-ops after following the above.
> git merge stage/dev300
Is that stage/ooo/dev300?
>
> I get this output from the merge:
I get thousands of conflicts. Have the branches moved since your post?
It may be better to give us sha1 or stable tags.
Are you doing any builds before merging?
> PS. of course, perhaps this is 'just me' - for space / time /
> simplicty / certainty reasons, I do a lot of "cp -lR foo/.git baa/" to
> duplicate trees - but AFAIK all git operations are atomic and use
> renames rather than in-place re-writing: right ?
Ouch. See Brian's post :)
Michael
next prev parent reply other threads:[~2011-02-22 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:34 libreoffice merge(tool?) issue #3 Michael Meeks
2011-02-22 15:55 ` Brian Gernhardt
2011-02-24 16:39 ` libreoffice merge(tool?) issue #3 ... (bogus) Michael Meeks
2011-02-25 10:08 ` Michael J Gruber
2011-02-25 20:55 ` Andres Freund
2011-02-28 14:25 ` copying git repositories Michael Meeks
2011-02-28 15:03 ` Andres Freund
2011-02-28 15:10 ` Brian Gernhardt
2011-02-22 17:30 ` Michael J Gruber [this message]
2011-02-22 18:14 ` libreoffice merge(tool?) issue #3 Michael Meeks
2011-02-23 11:18 ` Michael J Gruber
2011-02-23 13:22 ` 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=4D63F2C5.2080505@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=kendy@novell.com \
--cc=michael.meeks@novell.com \
--cc=nthiebaud@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 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).