All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: git issue
Date: Wed, 1 Jul 2015 10:21:41 -0400	[thread overview]
Message-ID: <20150701142141.GA11460@codemonkey.org.uk> (raw)
In-Reply-To: <5593ED2C.50705@gmx.de>

On Wed, Jul 01, 2015 at 03:37:48PM +0200, Toralf Förster wrote:
 > got today :
 > 
 > $ cd ~/devel/trinity; git pull                       
 > U       blockdevs.c
 > U       debug.c
 > U       rand/random-pathname.c
 > U       rand/random.c
 > U       shm.c
 > U       tools/analyze-sockets.c
 > U       uid.c
 > Pull is not possible because you have unmerged files.
 > Please, fix them up in the work tree, and then use 'git add/rm <file>'
 > as appropriate to mark resolution and make a commit.
 > 
 > 
 > tfoerste@t44 ~/devel/trinity $ git diff
 > 
 > tfoerste@t44 ~/devel/trinity $ git status
 > On branch master
 > Your branch and 'origin/master' have diverged,
 > and have 3702 and 3711 different commits each, respectively.
 >   (use "git pull" to merge the remote branch into yours)
 > You have unmerged paths.
 >   (fix conflicts and run "git commit")

I wondered if anyone would notice this.
I edited history to fix up two broken commit dates.

Just reclone. Shouldn't happen again.

	Dave

  reply	other threads:[~2015-07-01 14:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 13:37 git issue Toralf Förster
2015-07-01 14:21 ` Dave Jones [this message]
2015-07-01 15:11   ` Toralf Förster
  -- strict thread matches above, loose matches on Subject: below --
2016-11-01 10:28 Git issue Halde, Faiz
2016-11-01 17:45 ` Jeff King
2016-11-01 18:11   ` Junio C Hamano
2016-11-01 20:50   ` Philip Oakley
2016-11-01 21:03     ` Jeff King
2016-11-01 21:23       ` Junio C Hamano
2016-11-04  4:52         ` Jacob Keller

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=20150701142141.GA11460@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=toralf.foerster@gmx.de \
    --cc=trinity@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.