From: layer <layer@known.net>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: need help with git show :1:...
Date: Wed, 08 Apr 2009 11:10:09 -0700 [thread overview]
Message-ID: <7357.1239214209@relay.known.net> (raw)
In-Reply-To: <51419b2c0904081107s7ba08367w671d5b494095402@mail.gmail.com>
Elijah Newren <newren@gmail.com> wrote:
>> Hi,
>>
>> On Wed, Apr 8, 2009 at 12:02 PM, layer <layer@known.net> wrote:
>> > Elijah Newren <newren@gmail.com> wrote:
>> >>> Does the file have conflicts? Try
>> >>> git ls-files -s src/c/sock.c
>> >
>> > Yes, it did have conflicts. I resolved the conflicts via editing, but
>> > want to look at the other versions before finalizing the edits.
>> >
>> > quadra% git ls-files -s src/c/sock.c
>> > 100644 ef6c9b94c678dc79760edfd15a0796b3726b76f6 0 src/c/sock.c
>>
>> That suggests that the file is not unmerged, i.e. that there aren't
>> any remaining conflicts. This explains why your commands wouldn't
>> work unless you used stage 0 instead of 1 or 2. Now, why there
>> weren't conflicts when you thought there were? I have no idea, unless
>> perhaps you did a stray git add src/c/sock.c.
It was several of weeks ago that I started this merge, and I remember
playing with git show then and it worki. I might have overwriten
the file with one of the show's and done manual editing that way. I
don't know if this makes a difference.
How can I redo the merge for just this file? Is that possible? I
think I'd definitely like to start over on *just this one file*.
Thanks.
next prev parent reply other threads:[~2009-04-08 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 17:41 need help with git show :1: layer
2009-04-08 17:58 ` Elijah Newren
2009-04-08 18:02 ` layer
2009-04-08 18:07 ` Elijah Newren
2009-04-08 18:10 ` layer [this message]
2009-04-08 18:25 ` Elijah Newren
2009-04-08 18:35 ` layer
2009-04-08 18:38 ` Elijah Newren
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 17:57 layer
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=7357.1239214209@relay.known.net \
--to=layer@known.net \
--cc=git@vger.kernel.org \
--cc=newren@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 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.