From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Sylwester Nawrocki' <sylvester.nawrocki@gmail.com>
Subject: Re: [GIT PULL] Samsung cleanup-2 for v3.6
Date: Fri, 20 Jul 2012 09:05:49 +0000 [thread overview]
Message-ID: <201207200905.50396.arnd@arndb.de> (raw)
In-Reply-To: <194e01cd65fc$ce163be0$6a42b3a0$%kim@samsung.com>
On Thursday 19 July 2012, Kukjin Kim wrote:
> > 2. If you can, please use signed tags for your pull requests rather
> > than branch names. A signed tag means that you can write the text
> > for the merge changeset yourself so I don't have to do the description.
> > Ideally the signing key should have signatures from other people in the
> > keyring so everybody can check the authenticity of the request, but
> > just having the changelog there also helps.
> >
> OK, I see. I will try to use it as per your suggestion. But I'm not familiar
> with that now. So if you don't mind I'd like to send signed tag from next
> merge window :-)
No problem. It's not a big difference to me anyway. I suppose by then we will
also have had the chance for keysigning at the ARM mini summit.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung cleanup-2 for v3.6
Date: Fri, 20 Jul 2012 09:05:49 +0000 [thread overview]
Message-ID: <201207200905.50396.arnd@arndb.de> (raw)
In-Reply-To: <194e01cd65fc$ce163be0$6a42b3a0$%kim@samsung.com>
On Thursday 19 July 2012, Kukjin Kim wrote:
> > 2. If you can, please use signed tags for your pull requests rather
> > than branch names. A signed tag means that you can write the text
> > for the merge changeset yourself so I don't have to do the description.
> > Ideally the signing key should have signatures from other people in the
> > keyring so everybody can check the authenticity of the request, but
> > just having the changelog there also helps.
> >
> OK, I see. I will try to use it as per your suggestion. But I'm not familiar
> with that now. So if you don't mind I'd like to send signed tag from next
> merge window :-)
No problem. It's not a big difference to me anyway. I suppose by then we will
also have had the chance for keysigning at the ARM mini summit.
Arnd
next prev parent reply other threads:[~2012-07-20 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:44 [GIT PULL] Samsung cleanup-2 for v3.6 Kukjin Kim
2012-07-16 21:44 ` Kukjin Kim
2012-07-17 20:58 ` Arnd Bergmann
2012-07-17 20:58 ` Arnd Bergmann
2012-07-19 22:21 ` Kukjin Kim
2012-07-19 22:21 ` Kukjin Kim
2012-07-20 9:05 ` Arnd Bergmann [this message]
2012-07-20 9:05 ` Arnd Bergmann
2012-07-21 11:33 ` Kukjin Kim
2012-07-21 11:33 ` Kukjin Kim
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=201207200905.50396.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sylvester.nawrocki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.