From: Andrew Morton <akpm@osdl.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@suse.cz, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [ALSA PATCH] HG repo sync
Date: Thu, 29 Jun 2006 03:56:27 -0700 [thread overview]
Message-ID: <20060629035627.a073290f.akpm@osdl.org> (raw)
In-Reply-To: <s5h4py4p7lz.wl%tiwai@suse.de>
On Thu, 29 Jun 2006 12:40:56 +0200
Takashi Iwai <tiwai@suse.de> wrote:
> > The tree I
> > get from
> > git+ssh://master.kernel.org/pub/scm/linux/kernel/git/perex/alsa-current.git
> > has quite different changes in it.
>
> Yes, alsa-current git contains more changes currently in ALSA HG
> repo. alsa git contains only (safe and important) changes for
> upstream.
I'll grab the mercurial tree, assuming that has everything in it?
How does one turn that into a patch against mainline?
prev parent reply other threads:[~2006-06-29 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 9:39 Jaroslav Kysela
2006-06-29 9:53 ` Andrew Morton
2006-06-29 10:40 ` Takashi Iwai
2006-06-29 10:48 ` Jaroslav Kysela
2006-06-29 10:56 ` 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=20060629035627.a073290f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
--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®