From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: drivers/char/sonypi.h broken
Date: Thu, 20 Sep 2001 08:18:45 -0600 [thread overview]
Message-ID: <200109201418.f8KEIjG01625@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E15k37E-0005CC-00@the-village.bc.nu>
In-Reply-To: <200109200401.f8K413n29745@vindaloo.ras.ucalgary.ca> <E15k37E-0005CC-00@the-village.bc.nu>
Alan Cox writes:
> > Yes, I'm annoyed. So much for syncing up tonight with -pre12, testing
> > (yeah, some of us still believe in TESTING), and thence onto coding.
> > I've spent the evening flushing out other people's turds. Grrr.
>
> Turn off the computer, go spend a day cooling down for god sake.
Well, I went to bed shortly after my missive :-)
> One header file disappeared in the email pile somewhere. Of course
> if you'd _bothered_ to check the l/k archive before ranting you'd
> have found the posting about it.
Hm. I got testy because there were three broken things I stumbled over
in 12 hours. I think this just highlights the need for BitKeeper or
equivalent, where automated regression testing (even a simple "does it
compile and link?") is performed, and if the test fails, it gets
bounced and doesn't even get to Linus.
Alan: I realise it's impractical for you to manually test each
patchlet that you send to Linus, since you carry a large number of
them. But would you consider an automated system? I'm thinking of a
script that you use to "mail" each patch to Linus. Said script applies
and compiles, and either bounces the patch, or sends it off the Linus.
That way you get the same fire-and-forget behaviour you have now with
email, but with better testing.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-09-20 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 4:01 Richard Gooch
2001-09-20 8:52 ` Stelian Pop
2001-09-20 12:39 ` Alan Cox
2001-09-20 14:18 ` Richard Gooch [this message]
2001-09-20 17:46 ` Alan Cox
2001-09-20 18:10 ` Richard Gooch
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=200109201418.f8KEIjG01625@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®