netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: PATCH: rtnetlink explicit flags setting
Date: Tue, 31 May 2005 05:39:51 -0400	[thread overview]
Message-ID: <1117532391.6134.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20050528161637.GT15391@postel.suug.ch>

On Sat, 2005-28-05 at 18:16 +0200, Thomas Graf wrote:
> * jamal <1117296041.19563.6.camel@localhost.localdomain> 2005-05-28 12:00
> > > I just tested both patches for about 30 minutes. Everything OK. Feel
> > > free to apply the patches.
> > 
> > We have another problem. What tree is this against? Both patches have
> > failures patching against latest davem and linus git trees.
> 
> It's against my davem-pending tree which should reflect the current
> state of davem's tree so they _should_ apply on his side. In this
> specific case you're probably missing the neighbour table patches.


Now you really have to send some swiss chocolate over ;->
It still doesnt apply to Davems latest tree.

> Basically I produce diffs this way:
> 
> separate tree per patchset -> merge into  testing tree ->
> testing period -.  merge into $person-pending -> extraction
> of patches and submission.
> 

Almost very close to what i do - which could be improved or you keep a
few hundred trees. Jeff Garzik (some email to netdev with a HOWTO ) was
talking about some new scheme where instead of trees you use branches of
the same tree. I didnt quiet follow his trick.

> I was trying to get some more quality control into my workflow,
> so I started testing patches for 3-4 weeks to avoid fallouts
> but apparently this is failing miserably at the moment due to
> some broken scripts of mine.

I think the problem in this case was you had already commited to that
tree your changes that you sent to Dave. And the tree you were using as
a base for generating the patch was only something you and Dave know
about.

cheers,
jamal

  reply	other threads:[~2005-05-31  9:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 12:32 PATCH: rtnetlink explicit flags setting jamal
2005-05-27 12:50 ` Thomas Graf
2005-05-27 13:58   ` jamal
2005-05-27 14:13     ` Thomas Graf
2005-05-27 15:01       ` jamal
2005-05-27 15:19         ` Thomas Graf
2005-05-27 15:57           ` jamal
2005-05-27 16:59             ` Thomas Graf
2005-05-27 17:00               ` [PATCH 1/2] [NETLINK] Introduce NLMSG_NEW macro to better handle netlink flags Thomas Graf
2005-05-27 17:01               ` [PATCH 2/2] [NETLINK] Correctly set NLM_F_MULTI without checking the pid Thomas Graf
2005-05-28  1:06                 ` jamal
2005-05-31 22:37                 ` David S. Miller
2005-05-28  1:12               ` PATCH: rtnetlink explicit flags setting jamal
2005-05-28  1:28                 ` Thomas Graf
2005-05-28  1:48                   ` jamal
2005-05-28 12:18                     ` Thomas Graf
2005-05-28 16:00                       ` jamal
2005-05-28 16:16                         ` Thomas Graf
2005-05-31  9:39                           ` jamal [this message]
2005-05-31  9:41                             ` who 王海
2005-05-31 21:43 ` PATCH: rtnetlink explicit flags setting David S. Miller
2005-05-31 22:26   ` Thomas Graf
2005-05-31 22:31     ` David S. Miller
2005-06-02 13:04       ` PATCH: explicit typing WAS(Re: " jamal
2005-06-02 13:30         ` jamal
2005-06-03  5:08         ` David S. Miller

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=1117532391.6134.13.camel@localhost.localdomain \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=tgraf@suug.ch \
    /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;
as well as URLs for NNTP newsgroup(s).