From: Rene Herman <rene.herman@keyaccess.nl>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: New conflict message in latest GIT
Date: Wed, 23 Jul 2008 20:38:40 +0200 [thread overview]
Message-ID: <48877AB0.6090100@keyaccess.nl> (raw)
In-Reply-To: <b637ec0b0807231111o133ad391k79acceb777c2e7a6@mail.gmail.com>
On 23-07-08 20:11, Fabio Comolli wrote:
> But definitely this is Linus' tree.
I failed to delete the "g" prefix I see. In any case, fine, this is not
helping then. Butting out...
Rene.
next prev parent reply other threads:[~2008-07-23 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:56 New conflict message in latest GIT Fabio Comolli
2008-07-22 20:00 ` Rene Herman
2008-07-22 20:14 ` Rene Herman
2008-07-23 7:17 ` Fabio Comolli
2008-07-23 8:01 ` Rene Herman
2008-07-23 18:11 ` Fabio Comolli
2008-07-23 18:38 ` Rene Herman [this message]
2008-07-23 18:56 ` Bjorn Helgaas
2008-07-23 19:50 ` Fabio Comolli
2008-08-09 16:13 ` Jean Delvare
2008-08-09 16:32 ` Fabio Comolli
2008-08-09 17:03 ` Jean Delvare
2008-08-09 18:46 ` Fabio Comolli
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=48877AB0.6090100@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox