public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: linux-next: manual merge of the hdlc tree
Date: Fri, 17 Oct 2008 16:30:38 +0200	[thread overview]
Message-ID: <m3tzbbway9.fsf@maximus.localdomain> (raw)
In-Reply-To: <20081017165046.b5a05953.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Fri\, 17 Oct 2008 16\:50\:46 +1100")

Hi Stephen,

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Today's linux-next merge of the hdlc tree got a conflict in
> Documentation/DocBook/Makefile between commit
> 7e3975617df8dd8b7fd94f14200abdec9f71729e ("Remove videobook.tmpl") from
> Linus' tree and commit 9c7205161b03a43861765a26fc72f5a00fdadf75 ("WAN:
> syncppp.c is no longer used by any kernel code. Remove it") from the hdlc
> tree.
>
> Overlapping changes.  I fixed it up (see below).

Thanks. I will update to have the latest Linus' tree.
-- 
Krzysztof Halasa

  reply	other threads:[~2008-10-17 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  5:50 linux-next: manual merge of the hdlc tree Stephen Rothwell
2008-10-17 14:30 ` Krzysztof Halasa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-13  4:21 Stephen Rothwell
2008-10-31  5:29 Stephen Rothwell
2008-10-31 17:50 ` Krzysztof Halasa
2008-11-01  0:54   ` Stephen Rothwell
2008-10-29  6:52 Stephen Rothwell
2008-07-08  7:27 Stephen Rothwell
2008-07-08  7:23 Stephen Rothwell
2008-07-04  8:56 Stephen Rothwell
2008-07-04  9: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=m3tzbbway9.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=corbet@lwn.net \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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