From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jaroslav Kysela <perex@suse.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA fixes #1
Date: Thu, 03 Oct 2002 19:04:49 -0400 [thread overview]
Message-ID: <3D9CCD11.3020506@pobox.com> (raw)
In-Reply-To: Pine.LNX.4.33.0210031241280.23619-100000@penguin.transmeta.com
Linus Torvalds wrote:
> On Thu, 3 Oct 2002, Jaroslav Kysela wrote:
>
>>>Note that BK really only helps if you are careful, and I can synchronize
>>>with your BK tree. The fact that your BK tree contains non-alsa stuff
>>
>>Please, remove the bksend script from Documentation/BK-usage/bksend .
>>You don't like it and it's completely crappy. BK does renumbering of
>>ChangeSets itselves. So everybody has different numbers for changesets.
The bksend script works just fine, provided you use it correctly...
I think the main use of the script is not merging with Linus but posting
public, reviewable BK patches.
> But if there is a clean tree to pull from, that is absolutely the
> preferred method for me to sync up, _especially_ with things like drivers.
> Then an email that just says
>
> Linus,
> please do
>
> bk pull .....
>
> to receive changes to the following files
>
> .. diffstat list ..
>
> through the following changes
>
> .. changset list ..
>
> and then I don't even need to see the diffs themselves if I can just see
> that it only touches the ALSA files (that's another reason why I really
> want clean trees - immediately that there is a changeset to a non-ALSA
> file I want to see diffs, so that I have a clue about potential conflicts)
And "Documentation/BK-usage/bk-make-sum ~/repo/linus-2.5" helpfully
generates this output ;-)
Jeff
prev parent reply other threads:[~2002-10-03 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:09 [PATCH] ALSA fixes #1 Jaroslav Kysela
2002-10-03 15:37 ` Linus Torvalds
2002-10-03 19:31 ` Jaroslav Kysela
2002-10-03 19:52 ` Linus Torvalds
2002-10-03 23:04 ` Jeff Garzik [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=3D9CCD11.3020506@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.