All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: GIT: something wrong with sound-2.6/devel?
Date: Mon, 21 Jul 2008 12:39:05 +0200	[thread overview]
Message-ID: <48846749.7070906@keyaccess.nl> (raw)
In-Reply-To: <20080721095119.GD7083@sirena.org.uk>

On 21-07-08 11:51, Mark Brown wrote:

> On Mon, Jul 21, 2008 at 10:45:29AM +0200, Rene Herman wrote:
> 
>> rene@7ixe4:~/src/linux/7ixe4$ git fetch tiwai
>>  From git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
>>   ! [rejected]        devel      -> tiwai/devel  (non fast forward)
>>   ! [rejected]        dma-fix    -> tiwai/dma-fix  (non fast forward)
>>   ! [rejected]        master     -> tiwai/master  (non fast forward)
> 
>> I'll go ask on the GIT list what this might be about...
> 
> This means that the git remote is configured to only pull fast forwards
> from that repository.  Add a + to the 'fetch =' for it in .git/config
> and it'll track non-linear updates like you get when the remote rebases.

I see.... thanks. I'll wait a bit with doing that then since it appears 
that this rejection might be the behaviour I want from it -- am using 
the devel branch specifically due to it only being rebased at releases.

Okay, thanks again, I get it. Things work again without anything special 
after a "git remote rm tiwai, git remote add tiwai <url>" cycle. That's 
ofcourse pretty horrible though. Really convinced by now that public 
repos that downstream users might have pulled should just not be 
rebased. Okay, the once per cycle as with that devel branch is probably 
okay but in essence any tree you rebase becomes a throw away tree that 
noone other than your upstream has any use for longer than once.

I'll keep the question on the GIT list outstanding due to the difference 
with "git pull" which I do still find unexpected.

Rene.

  reply	other threads:[~2008-07-21 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 18:56 GIT: something wrong with sound-2.6/devel? Rene Herman
2008-07-20 19:08 ` Jaroslav Kysela
2008-07-20 19:35   ` Rene Herman
2008-07-20 20:04   ` Rene Herman
2008-07-21  8:45     ` Rene Herman
2008-07-21  9:51       ` Mark Brown
2008-07-21 10:39         ` Rene Herman [this message]
2008-07-21 10:47           ` Mark Brown

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=48846749.7070906@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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 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.