linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC+CFT] Use word operations in bitops
Date: Tue, 18 Jan 2011 16:28:58 +0000	[thread overview]
Message-ID: <20110118162858.GA17398@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110118155851.GC10686@pengutronix.de>

On Tue, Jan 18, 2011 at 04:58:51PM +0100, Uwe Kleine-K?nig wrote:
> Hello Russell,
> 
> On Tue, Jan 18, 2011 at 03:43:44PM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 18, 2011 at 04:32:57PM +0100, Uwe Kleine-K?nig wrote:
> > > On Mon, Jan 17, 2011 at 10:46:18AM +0000, Russell King - ARM Linux wrote:
> > I will continue to mail out patches which I want people to test and give
> > feedback on, because that is the _only_ way to do it.
> Note that I didn't suggest to stop sending out patches and collecting
> the acks and tested-bys there.  The automated tests are just a different
> test.
> 
> And IMHO it's not harder to reply with a git commit-id, but it makes it
> more likely that a reply to a wrong mail is detected.

No.  Take a moment and think.

Two people pull the commits one evening.  One gets in during GMT morning,
checks their tests, and reports "git commit X passed, have this Tested-by".
So, their tested-by is added to the commit, which changes the git ID to
Y.

Second person gets in during GMT afternoon, and reports "git commit X
passed."  Now instead of looking in the current branch, I'd have to
cross-reference it back to what was originally there, check that's
what they actually meant, look that up in the new branch, and apply
their tested-by to that instead.

More complicated means more things to go wrong.  No thank you.

      reply	other threads:[~2011-01-18 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 12:19 [RFC+CFT] Use word operations in bitops Russell King - ARM Linux
2011-01-16 18:15 ` Russell King - ARM Linux
2011-01-17 11:03   ` Jamie Iles
2011-01-17  9:46 ` Jamie Iles
2011-01-17 10:08 ` Uwe Kleine-König
2011-01-17 10:46   ` Russell King - ARM Linux
2011-01-18 15:32     ` Uwe Kleine-König
2011-01-18 15:43       ` Russell King - ARM Linux
2011-01-18 15:58         ` Uwe Kleine-König
2011-01-18 16:28           ` Russell King - ARM Linux [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=20110118162858.GA17398@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).