From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Larry McVoy <lm@work.bitmover.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHES] today's batch of "nuking kernel/ksyms.c"
Date: Thu, 2 Oct 2003 06:44:59 -0300 [thread overview]
Message-ID: <20031002094459.GD1699@conectiva.com.br> (raw)
In-Reply-To: <20031002040206.GA2382@work.bitmover.com>
Em Wed, Oct 01, 2003 at 09:02:06PM -0700, Larry McVoy escreveu:
> If this is all the same idea why are you putting it in multiple changesets?
> Where I work we have a rule "one idea, one changeset", which makes it far
> easier to track down problems later.
Oh well, I thought it was better to slowly deconstruct the thing, started
sending, my feedback was that the trees are being pulled by Linus, so
everything seems to be allright, if Linus merged all of micro changesets as one
changeset I'd understand that as "stop sending as separate changesets, send me
just one", and I'd do just that, Linus?
- Arnaldo
prev parent reply other threads:[~2003-10-02 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 3:03 [PATCHES] today's batch of "nuking kernel/ksyms.c" Arnaldo Carvalho de Melo
2003-10-02 4:02 ` Larry McVoy
2003-10-02 9:44 ` Arnaldo Carvalho de Melo [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=20031002094459.GD1699@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox