From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Steve French <sfrench@us.ibm.com>
Subject: Re: Resolved merge conflicts in next-creds
Date: Mon, 11 Aug 2008 10:16:02 +1000 [thread overview]
Message-ID: <20080811101602.09555609.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LRH.1.10.0808110950530.3636@tundra.namei.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hi James,
On Mon, 11 Aug 2008 09:57:44 +1000 (EST) James Morris <jmorris@namei.org> wrote:
>
> I manually resolved the following conflicts in
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next-creds
>
> when merging with latest Linus. (This branch holds the creds API changes
> from David Howells and is being pulled into linux-next).
Thanks for that.
> The CIFS conflicts were collisions with API changes. I'm not sure how
> best to extract this information from git. 'git-rerere' doesn't seem to
> do anythig, even with:
>
> $ git-config --list
> rerere.enabled=1
"git rerere" works behind the scenes to fix up merge conflicts that you
have fixed once before. All it does is record the diff of conflicted
files after the merge fails and then the new versions of those files when
you do the next commit. I know of no way to get any useful information
out of it.
The git show below should, however, be sufficient and looks just like
what I did on Friday.
I have a plan for getting rid of these - I will start on it today or
tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-11 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 23:57 James Morris
2008-08-11 0:16 ` Stephen Rothwell [this message]
2008-08-11 5:35 ` Stephen Rothwell
2008-08-11 21:53 ` James Morris
2008-08-11 23:36 ` Stephen Rothwell
2008-08-12 9:27 ` David Howells
2008-08-12 11:19 ` Stephen Rothwell
2008-08-11 14:51 ` Steven French
2008-08-11 23:39 ` Stephen Rothwell
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=20080811101602.09555609.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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
all inboxes | Powered by JetHome®