From: Andrew Morton <akpm@osdl.org>
To: Martin Waitz <tali@admingilde.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docbook: fix escaping of kernel-doc
Date: Fri, 18 Mar 2005 03:22:55 -0800 [thread overview]
Message-ID: <20050318032255.6423144e.akpm@osdl.org> (raw)
In-Reply-To: <20050318111658.GM8617@admingilde.org>
Martin Waitz <tali@admingilde.org> wrote:
>
> ... and I really have to redo my bitkeeper repository as it
> is full of merge artifacts as BK did not note the fact that
> the patches were applied using normal patches.
Normally bk would handle that, but I have an irritating habit of stripping
off all the trailing whitespace which people keep trying to add to the
kernel.
> I guess I have to use one complete tree per patch and recreate
> the public repo as a combination of the individual ones.
> Alternatives?
Export all the csets as unified diffs, reapply them.
prev parent reply other threads:[~2005-03-18 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503112034.j2BKYMli008385@shell0.pdx.osdl.net>
[not found] ` <20050314081319.GD8617@admingilde.org>
[not found] ` <20050314004712.4746f2cf.akpm@osdl.org>
2005-03-18 11:16 ` Martin Waitz
2005-03-18 11:22 ` Andrew Morton [this message]
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=20050318032255.6423144e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tali@admingilde.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®