From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] HG -> GIT migration
Date: Wed, 21 May 2008 15:04:53 +0200 [thread overview]
Message-ID: <48341DF5.4090307@keyaccess.nl> (raw)
In-Reply-To: <s5hfxsbx27f.wl%tiwai@suse.de>
On 21-05-08 14:37, Takashi Iwai wrote:
> At Wed, 21 May 2008 14:30:31 +0200,
> Rene Herman wrote:
>> $ git remote show sound-2.6
>> * remote sound-2.6
>> URL: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
>> Tracked remote branches
>> master
>>
>> What's the status of that one now? Should I continue pulling that one or
>> should I switch to the new alsa-kernel GIT repo? I want to pull it into
>> a Linus clone tree...
>
> We are working on this right now. alsa.git is far currently behind my
> tree.
>
> One problem we hit is about multiple committers and rebase. If you do
> git-rebase, the commiter information is touched although the sign-off
> isn't updated. git-rebase looks apparently designed for the
> single-commiter model.
It's "worse" than that; rebasing is designed for a _private_ development
model. git-rebase is a very handy tool for people like myself (people
without a downstream that is) and it basically enables the quilt model
of a stack of patches on top of git but public trees that have people
pulling from them should generally not rebase or everyone who _is_
pulling finds a different tree each time.
Linus is vehement about this also. There have a few threads about it and
the most recent was:
http://lkml.org/lkml/2008/5/17/190
I'm also not an experienced git user (not other than in my own leafnode
developer mode, certainly) but I expect Linus might not terribly mind
answering a few questions about the model -- ALSA is a significant
subsystem and it switching to GIT might even make for a nice "this is
how you do that as a subsystem" treatise...
(ie, also added linux-kernel)
Rene.
next parent reply other threads:[~2008-05-21 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0805201314190.1798@tm8103-a.perex-int.cz>
[not found] ` <200805211430.06653.linux@audioscience.com>
[not found] ` <Pine.LNX.4.61.0805210805080.1798@tm8103-a.perex-int.cz>
[not found] ` <s5hve18vtml.wl%tiwai@suse.de>
[not found] ` <483415E7.5080402@keyaccess.nl>
[not found] ` <s5hfxsbx27f.wl%tiwai@suse.de>
2008-05-21 13:04 ` Rene Herman [this message]
2008-05-21 13:48 ` [alsa-devel] HG -> GIT migration Jaroslav Kysela
2008-05-21 14:40 ` Rene Herman
2008-05-21 14:52 ` Takashi Iwai
2008-05-21 15:29 ` Rene Herman
2008-05-22 1:24 ` Stephen Rothwell
2008-05-22 20:43 ` Rene Herman
2008-05-22 23:40 ` Stephen Rothwell
2008-05-21 14:47 ` Takashi Iwai
2008-05-21 15:40 ` Rene Herman
2008-05-21 16:02 ` Takashi Iwai
2008-05-21 16:16 ` Linus Torvalds
2008-05-21 16:51 ` Takashi Iwai
2008-05-21 17:43 ` Linus Torvalds
2008-05-21 18:11 ` Linus Torvalds
2008-05-21 18:25 ` david
2008-05-21 18:39 ` Linus Torvalds
2008-05-21 18:49 ` Takashi Iwai
2008-05-21 18:47 ` Takashi Iwai
2008-05-21 19:02 ` Linus Torvalds
2008-05-21 21:08 ` Takashi Iwai
2008-05-22 14:23 ` Dmitry Torokhov
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=48341DF5.4090307@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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