Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: HG vs GIT
Date: Fri, 08 Feb 2008 00:06:33 +1100	[thread overview]
Message-ID: <47AB0259.6060604@superbug.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0802071024530.8113@tm8103.perex-int.cz>

Jaroslav Kysela wrote:
> Hi,
>
> 	it seems that GIT matured somewhat. git-push has been implemneted. 
> It was main reason to not use GIT when we made decision between HG and 
> GIT.
> 	As we could have potential problems with branches in HG 
> repository, I would like to consider a switch to GIT althought it means 
> some changes in my scripts on ALSA server and my ksync tool.
> 	I just successfully tried (a bit modified hg-to-git.py script) and 
> it seems to be working properly.
> 	Any objections?
>
> 						Jaroslav
>   
I have no problem with moving to git.
Just so long as we can still create alsa-driver packages from it.
Will the git tree just be alsa-kernel, or will it be the entire linux 
kernel with the latest alsa additions?

James

  parent reply	other threads:[~2008-02-07 13:05 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
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 [this message]
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=47AB0259.6060604@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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