All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 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.

WARNING: multiple messages have this Message-ID (diff)
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.

  reply	other threads:[~2008-05-21 13:02 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 11:21 HG -> GIT migration Jaroslav Kysela
2008-05-20 14:12 ` Ben Stanley
2008-05-20 14:24   ` Jaroslav Kysela
2008-05-21  2:30 ` Eliot Blennerhassett
2008-05-21  6:09   ` Jaroslav Kysela
2008-05-21 10:28     ` Takashi Iwai
2008-05-21 12:30       ` Rene Herman
2008-05-21 12:37         ` Takashi Iwai
2008-05-21 13:04           ` Rene Herman [this message]
2008-05-21 13:04             ` [alsa-devel] " Rene Herman
2008-05-21 13:48             ` Jaroslav Kysela
2008-05-21 14:40               ` Rene Herman
2008-05-21 14:40                 ` [alsa-devel] " Rene Herman
2008-05-21 14:52                 ` Takashi Iwai
2008-05-21 14:52                   ` [alsa-devel] " Takashi Iwai
2008-05-21 15:29                   ` Rene Herman
2008-05-21 15:29                     ` [alsa-devel] " Rene Herman
2008-05-22  1:24                     ` Stephen Rothwell
2008-05-22 20:43                       ` Rene Herman
2008-05-22 20:43                         ` [alsa-devel] " Rene Herman
2008-05-22 23:40                         ` Stephen Rothwell
2008-05-22 23:40                           ` [alsa-devel] " Stephen Rothwell
2008-05-21 14:47             ` Takashi Iwai
2008-05-21 14:47               ` [alsa-devel] " Takashi Iwai
2008-05-21 15:40               ` Rene Herman
2008-05-21 15:40                 ` [alsa-devel] " Rene Herman
2008-05-21 16:02                 ` Takashi Iwai
2008-05-21 16:02                   ` [alsa-devel] " Takashi Iwai
2008-05-21 16:16                   ` Linus Torvalds
2008-05-21 16:51                     ` Takashi Iwai
2008-05-21 16:51                       ` [alsa-devel] " Takashi Iwai
2008-05-21 17:07                       ` Tobin Davis
2008-05-21 17:19                         ` Jaroslav Kysela
2008-05-21 17:22                         ` Rene Herman
2008-05-21 17:43                       ` [alsa-devel] " Linus Torvalds
2008-05-21 18:11                         ` Linus Torvalds
2008-05-21 18:11                           ` [alsa-devel] " Linus Torvalds
2008-05-21 18:25                           ` david
2008-05-21 18:39                             ` Linus Torvalds
2008-05-21 18:39                               ` [alsa-devel] " Linus Torvalds
2008-05-21 18:49                             ` Takashi Iwai
2008-05-21 18:49                               ` [alsa-devel] " Takashi Iwai
2008-05-21 18:47                         ` Takashi Iwai
2008-05-21 18:47                           ` [alsa-devel] " Takashi Iwai
2008-05-21 19:02                           ` Linus Torvalds
2008-05-21 19:02                             ` [alsa-devel] " Linus Torvalds
2008-05-21 21:08                             ` Takashi Iwai
2008-05-21 21:08                               ` [alsa-devel] " Takashi Iwai
2008-05-22 14:23               ` Dmitry Torokhov
2008-05-21 22:16     ` Eliot Blennerhassett
2008-05-23  2:31       ` Ben Stanley
2008-05-23  6:38         ` Jaroslav Kysela

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=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 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.