All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [pull request] heap reference and trivial build fixes
Date: Tue, 10 Nov 2009 17:24:24 +0100	[thread overview]
Message-ID: <4AF993B8.6090402@domain.hid> (raw)
In-Reply-To: <4AF964C2.3060206@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> The following changes since commit 6d7d6bc436ef3d1fb51fa8de06d4ecf004e3b6a5:
>>>>   Gilles Chanteperdrix (1):
>>>>         nucleus: defer selector block deletion to an APC.
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   git://git.xenomai.org/xenomai-jki.git for-upstream
>>>>
>>>> Jan Kiszka (2):
>>>>       nucleus: Track heap mapping on to mm-clone
>>>>       nucleus: Fix trivial build warning
>>>>
>>>>  ksrc/nucleus/heap.c   |   12 +++++++++++-
>>>>  ksrc/nucleus/module.c |    2 +-
>>>>  2 files changed, 12 insertions(+), 2 deletions(-)
>>> Hi Jan,
>>>
>>> do you agree if I add the notification to the xenomai-git mailing list
>>> for your tree? It makes it possible to review your patches without any
>>> action on your side. Note that a recent modification to the notification
>>> mechanism only shows the relevant patches.
>>>
>> No problem. Ah, the new filter looks nice!
>>
>> And how would my new workflow look like? Just silently push into
>> 'for-upstream'?
> 
> Well, it does not work for me, because I always realize that I screwed
> up AFTER I push the changes. Besides, we may push things only for
> review, so, I would keep the pull requests and the discussions on the
> list, only avoid publishing the patches manually on the list. But this
> is open for discussion of course.

Fine with me as well, specifically as I tend to face similar problems.
And as one can pick the patches for citing from xenomai-git, commenting
on patching shouldn't be much harder for the reviewer.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-11-10 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 20:36 [Xenomai-core] [pull request] heap reference and trivial build fixes Jan Kiszka
2009-11-10 11:01 ` Gilles Chanteperdrix
2009-11-10 12:05   ` Jan Kiszka
2009-11-10 13:04     ` Gilles Chanteperdrix
2009-11-10 16:24       ` Jan Kiszka [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=4AF993B8.6090402@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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 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.