Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: HG vs GIT
Date: Thu, 07 Feb 2008 17:03:03 +0100	[thread overview]
Message-ID: <s5hwspgycso.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0802070731570.9968@shell4.speakeasy.net>

At Thu, 7 Feb 2008 07:49:39 -0800 (PST),
Trent Piepho wrote:
> 
> On Thu, 7 Feb 2008, Takashi Iwai wrote:
> > At Thu, 7 Feb 2008 14:52:43 +0100 (CET),
> > > > > How do I test the driver if it's compiled with the kernel in the alsa.git
> > > > > tree?  I want to compile the driver against the kernel I'm running now.
> > > >
> > > > Well, I don't get your point.  "git-pull alsa.git" onto your current
> > > > kernel tree and make.  Then you have the latest ALSA drivers for your
> > > > current system...
> > >
> > > Pull cannot be used. You'll pull also Linus's changes in tree with this
> > > command (which might not be wanted).
> >
> > Ah, OK, I didn't think that your current tree is behind the ALSA
> > tree.  But surely there must be an easy way to do that.  At easiest,
> > I'd make a diff of alsa-git.tree to the upstream and apply it over the
> > local tree.
> 
> It would have to be behind the current tree, unless you reboot multiple
> times per day.

What a shame :)

> The problem with an out of tree codebase extracted from git (or Hg), is
> that once extracted you couldn't use ALSA's SCM on it.  E.g., generating
> nice patches based on current head, or pulling and merging recent patches
> in with your current work.

It's possible to extract and merge patches nicely with git.  I just
pointed the "easiest" way to get the latest code.  There must be a
better way.


Takashi

  reply	other threads:[~2008-02-07 16:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  9:37 HG vs GIT Jaroslav Kysela
2008-02-07 11:27 ` Takashi Iwai
2008-02-07 11:45   ` Andrew Paprocki
2008-02-07 12:03     ` Takashi Iwai
2008-02-07 12:19       ` Jaroslav Kysela
2008-02-07 15:13         ` Takashi Iwai
2008-02-07 13:10       ` Trent Piepho
2008-02-07 13:26         ` Takashi Iwai
2008-02-07 13:41           ` Trent Piepho
2008-02-07 13:48             ` Takashi Iwai
2008-02-07 13:52               ` Jaroslav Kysela
2008-02-07 14:05                 ` Takashi Iwai
2008-02-07 14:07                   ` Jaroslav Kysela
2008-02-07 15:49                   ` Trent Piepho
2008-02-07 16:03                     ` Takashi Iwai [this message]
2008-02-07 19:46                       ` Mark Brown
2008-02-07 20:36                         ` Takashi Iwai
2008-02-08  0:42                           ` Mark Brown
2008-02-08  1:09                             ` Tobin Davis
2008-02-07 14:49               ` Tobin Davis
2008-02-07 15:00         ` Mark Brown
2008-02-07 15:18           ` Takashi Iwai
2008-02-07 16:03           ` Trent Piepho
2008-02-07 19:27             ` Mark Brown
2008-02-10 20:17         ` AK4114 - listing regs in proc - PATCH Pavel Hofman
2008-02-11 13:47           ` Takashi Iwai
2008-02-07 15:22       ` HG vs GIT Timur Tabi
2008-02-07 16:09         ` Takashi Iwai
2008-02-07 12:03   ` Jaroslav Kysela
2008-02-07 21:14   ` Rene Herman
2008-02-07 11:39 ` Mark Brown
2008-02-07 13:06 ` James Courtier-Dutton
2008-02-07 15:20 ` Timur Tabi
2008-02-07 15:53 ` Clemens Ladisch
2008-02-07 21:12 ` Rene Herman

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=s5hwspgycso.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=xyzzy@speakeasy.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