All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rene Herman <rene.herman@keyaccess.nl>
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 11:47:46 +0100	[thread overview]
Message-ID: <20080721104744.GA24668@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <48846749.7070906@keyaccess.nl>

On Mon, Jul 21, 2008 at 12:39:05PM +0200, Rene Herman wrote:
> On 21-07-08 11:51, Mark Brown wrote:
>> On Mon, Jul 21, 2008 at 10:45:29AM +0200, Rene Herman wrote:

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

It probably doesn't hurt to track the current state of the remote anyway
- even if the remote is rebased that won't affect the history of your
development branch and I can't off-hand think of a reason why it'd be
best to have the old status hanging around for a repo like this.

> ofcourse pretty horrible though. Really convinced by now that public repos
> that downstream users might have pulled should just not be rebased.  Okay,

Yes, that's the strongly expressed recommendation for things people
might want to base work on.

      reply	other threads:[~2008-07-21 10:47 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
2008-07-21 10:47           ` Mark Brown [this message]

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=20080721104744.GA24668@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --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 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.