public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Linus Walleij <linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Sundar R Iyer
	<sundar.iyer-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Subject: Re: [PATCH 1/4] i2c-nomadik: documentation fixes
Date: Wed, 29 Sep 2010 00:08:08 +0100	[thread overview]
Message-ID: <20100928230808.GM21564@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTikjUyxLaEURVh-42T9NL_XCvwPLU6pobV1yq2BD-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Sep 28, 2010 at 10:55:37AM +0200, Linus Walleij wrote:
> 2010/9/28 Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>:
> 
> > It means that if your tree is handling external patches, then you could end
> > up with the situation where it is difficult or almost impossible to undo
> > a change which the original sender either did not have the authority to
> > send, or has something in that should have never been sent (i've seen
> > several issues where companies have had desperate back-peddling because
> > someone forgot to remove some $secret from the repository before allowing
> > it to be uploaded somewhere).
> 
> We actually have that part under control, believe it or not :-)

Ok, but it is probably useful for other people out there.
 
> > It would have been helpful to add a 'From:' line as well, git can be
> > made to re-write the authour of a patch, but you'll have to search for
> > it. Please find a method for future reference.
> 
> I'm on it... thanks Ben.

My personal view is to always keep attributions. Even if they are then
posted through someone else, or require a corporate stamp on them before
they get out of the building.

Let me know what you'd like to do, and I'll sort out something for -next.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  parent reply	other threads:[~2010-09-28 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23  7:03 [PATCH 1/4] i2c-nomadik: documentation fixes Linus Walleij
     [not found] ` <1285225420-916-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2010-09-27  0:25   ` Ben Dooks
     [not found]     ` <20100927002508.GF21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-09-27  8:59       ` Linus Walleij
     [not found]         ` <AANLkTim_O65ZKod8oSV245Zu3saEwjcitPw3twSO5NrX-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-27  9:01           ` Sundar R IYER
2010-09-27 22:35           ` Ben Dooks
     [not found]             ` <20100927223509.GI21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-09-28  8:55               ` Linus Walleij
     [not found]                 ` <AANLkTikjUyxLaEURVh-42T9NL_XCvwPLU6pobV1yq2BD-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-28 23:08                   ` Ben Dooks [this message]
     [not found]                     ` <20100928230808.GM21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-09-29 22:53                       ` Linus Walleij

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=20100928230808.GM21564@trinity.fluff.org \
    --to=ben-i2c-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
    --cc=linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sundar.iyer-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.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