From: Tobin Davis <tdavis@dsl-only.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Rene Herman <rene.herman@keyaccess.nl>, alsa-devel@alsa-project.org
Subject: Re: HG -> GIT migration
Date: Wed, 21 May 2008 10:07:46 -0700 [thread overview]
Message-ID: <1211389666.8312.127.camel@razman> (raw)
In-Reply-To: <s5htzgrvbvo.wl%tiwai@suse.de>
I updated the Developers Zone wiki to reflect the new source repository,
making it a little easier to find.
Question: How do we get rss feeds? Is it similar to the HG method? I
like being able to monitor the updates via rss, to determine when I need
to refresh my tree, as I only really work on the hda-intel stuff at the
moment.
Tobin
On Wed, 2008-05-21 at 18:51 +0200, Takashi Iwai wrote:
> At Wed, 21 May 2008 09:16:05 -0700 (PDT),
> Linus Torvalds wrote:
> >
> >
> >
> > On Wed, 21 May 2008, Takashi Iwai wrote:
> > >
> > > But, this means that the fixes done outside the subsystem tree cannot
> > > be in the subsystem tree itself until the next release. It's a pretty
> > > weird situation.
> >
> > No it is NOT.
> >
> > Why should you have stuff from outside the subsystem tree?
>
> Well, what I meant is about the fixes to the subsystem (say, ALSA) by
> people in the outside. Not every ALSA-bugfix patch goes into the
> upstream from ALSA tree. You, Andrew and others pick individually
> ALSA-fix patches. They will be missing in the ALSA subsystem tree.
>
> And, what if that you need a fix for the fix that isn't in ALSA
> tree...? IMO, either a rebase or a merge is better than
> cherry-picks.
>
> > And quite frankly, the only reason to *need* those fixes in the first
> > place is if you merge random test-kernels during the merge window. What
> > you should strive for is to merge at the stable point, not random kernels
> > to keep you "up-to-date", and suddenly you don't need to make more merges
> > just to get (possibly) new fixes.
> >
> > See?
> >
> > If it's the ALSA tree, then what is it doing pulling all the random other
> > stuff that I merge?
> >
> > In other words - merging my random stuff, THAT is the "weird situation".
> > You should be doing ALSA development, not "random kernel" development.
>
> Hmm, that makes me thinking of the development model.
> We can leave ALSA tree without upstream fixes as is if user always
> pull both ALSA and upstream trees. This works for users that are
> using the latest development kernel.
>
> > > The method Linus suggested is suitable for random patches like tirival
> > > tree, but apparently not for every case.
> >
> > Umm. Bigger subsystems than ALSA are successfully using it and have no
> > problems, and don't think they need to merge backwards:
> >
> > [torvalds@woody linux]$ git rev-list v2.6.25.. drivers/net/ | wc -l
> > 739
> > [torvalds@woody linux]$ git rev-list v2.6.25.. sound/ | wc -l
> > 291
> >
> > iow, the only reason you seem to think that you need to merge more is that
> > you merged too much, or from a too-unstable base, to begin with.
> >
> > Aim for basing things on releases, or at least for merging just at stable
> > points (and only when you *need* to, and it will make your life much
> > easier. And the history will automatically be cleaner and less confusing.
>
> Yes, I see the point.
>
> But, my question is about the divergence between the development and
> for-linus branches: how to apply patches that exist only in for-linus
> tree back.
>
>
> thanks,
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Tobin Davis
What PROGRAM are they watching?
next prev parent reply other threads:[~2008-05-21 17:07 UTC|newest]
Thread overview: 36+ 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
2008-05-21 13:48 ` [alsa-devel] " 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 ` [alsa-devel] " 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 ` [alsa-devel] " Linus Torvalds
2008-05-21 16:51 ` Takashi Iwai
2008-05-21 17:07 ` Tobin Davis [this message]
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:25 ` [alsa-devel] " 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 ` [alsa-devel] " 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=1211389666.8312.127.camel@razman \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=rene.herman@keyaccess.nl \
--cc=tiwai@suse.de \
/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