All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Thomas De Schampheleire <patrickdepinguin+xenomai@domain.hid>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] xenomai-forge git woes
Date: Mon, 07 Nov 2011 15:19:20 +0100	[thread overview]
Message-ID: <4EB7E8E8.2030201@domain.hid> (raw)
In-Reply-To: <CAAXf6LWx0TdgzmdhZMMxKFWTxzZUP3FXgigmBh-iE78SrMC0eg@domain.hid>

On 11/07/2011 02:38 PM, Thomas De Schampheleire wrote:
> Hi,
>
> It seems something was up with the Xenomai-forge git repository. On
> the web interface, I see many old commits being recommitted today.
>
> Can you give some background information as to why this happened?
> And more importantly, not being an experienced git user, how to
> recover from it? 'git status' shows:
>
> # On branch master
> # Your branch and 'origin/master' have diverged,
> # and have 177 and 360 different commit(s) each, respectively.
>
> and a 'git pull' shows tons of conflicts on files I did not touch.
>

This is a rebase, which breaks the commit history. I have to rebase the 
-forge over the 2.6.x branch until the latter leaves the development 
phase at least. Cherry picking lots of changes manually from 2.6.x while 
it is under active development would be too error prone.

Now that 2.6.0 is out, the number of rebases should decrease 
significantly, until 2.6.1 is released, at which point they should stop.

You should force-pull your master branch, assuming you did not add any 
of your changes there, then rebase your own -forge update branch if any, 
onto the new master.

> Thanks,
> Thomas
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>


-- 
Philippe.


      reply	other threads:[~2011-11-07 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 13:38 [Xenomai-help] xenomai-forge git woes Thomas De Schampheleire
2011-11-07 14:19 ` Philippe Gerum [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=4EB7E8E8.2030201@domain.hid \
    --to=rpm@xenomai.org \
    --cc=Xenomai-help@domain.hid \
    --cc=patrickdepinguin+xenomai@domain.hid \
    /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.