linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 8/9] ARM: SoC defconfig changes for 3.19
Date: Wed, 10 Dec 2014 12:16:44 +0100	[thread overview]
Message-ID: <2480052.Mq2bie8eJI@wuerfel> (raw)
In-Reply-To: <CAMuHMdW35QRFmTMvtfx_1ZHn1W8a_LMPFFWuZgtXGfKEQDddzQ@mail.gmail.com>

On Wednesday 10 December 2014 09:56:55 Geert Uytterhoeven wrote:
> Hi Arnd,
> 
> On Tue, Dec 9, 2014 at 10:43 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
> >
> >   Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
> >
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/defconfig-for-linus
> 
> On https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git/, the
> "Download" column for all tags shows "tag <abbrev>...".
> Clicking on any of them gives e.g.:
> 
>     https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git/tag/?id=066ae43e621090340384ab3751b68306c49cd503
>     Bad tag reference: 066ae43e621090340384ab3751b68306c49cd503
> 
> In other repositories
> (e.g. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/), the
> "Download" column for tags shows "commit <abbrev>...", and the links behind
> them do work.
> 
> Note that if I s/tag/commit/ in the URL, it does work.
> 
> Is this an issue with your repository? Or does cgit on kernel.org needs to
> be updated for a new feature?

Very interesting. I suspect it's because I did something funny, but I don't
know if what I did was actually wrong or if cgit is wrong here, or possibly
both.

This is what I did:

- I wrote the tag descriptions on my main build machine, as an annotated but
  not signed tag, since this machine does not have my gpg key on it,
  using git-2.1.0

- I uploaded the unsigned tags to the arm-soc git tree and downloaded them
  on the machine that does have my signing keys.

- For each tag I did 'git tag -fs $TAG $TAG' and signed the existing tag
  description with my gpg key, using git-1.8.1.2

- I uploaded the updated tags back to the public tree

>From looking at the tag now (e.g. git show arm64-for-linus), it seems
the third step ended up signing a tag that points to another tag instead
of a commit:

> tag arm64-for-linus
> Tagger: Arnd Bergmann <arnd@arndb.de>
> Date:   Tue Dec 9 17:31:38 2014 +0100
> 
> ARM64: SoC changes for 3.19
> 
> This adds support for two new ARM64 platforms:
> 
> * ARM Juno
> * AMD Seattle
> 
> We had submissions for a number of additional platforms
> from Samsung, Freescale and Spreadtrum but are still working
> out the best process for getting these merged.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQIVAwUAVIcj62CrR//JCVInAQKv9w/+LXBBfJbNetHE17PoeV10O+ni6a3Xuv7F
> ZIkx+GgxEYT/8JPBeORUs0Boa6llpsUpn+GqCuqhMmFAPImxoQJ1ULmf6SFfbppB
> b7FRNoaW5GPUsi6mDfat4w3yXZK3LX0qlPprym1d9yGOXN9hnH8LkvnSsqZM1Ntn
> 4jnj7nQJyn/BG5OyFDWnTsyO7dIYMLm90s/VnVPxu7VGacDEnhAXdvqQkzkmavTK
> K9zOBYa4vGhfYM7Wy/3xQrJfHTZOkLOQh4TGwfCQjDoFxvhCXrDo7fU+TKdawq10
> KGHbxj8rhCaAUhc0Gqn77/Cri3LXGJyw+97VZeh9KWR1a1YAV5nsCvz3sZuQY78J
> qbTOwMq9xQ3nQnerkmGPeGV/UyouvdxO/SnOyZnTU0OaYJlFIbsdu8mIUH4xHkGm
> +7DceBhuDk+iVgDtULKpz0RA4XNsUV81Cb6FyVgmEcnuThRtCDetrN7RpMKmqynA
> ZQ/VM/0qtnzQp+XYIxJf7A6iexVtJp00Yffw7y0F8QaoBCwWEsPA1TMk4wPirCYn
> tsQ9C0jYKAWAI8scYpThiTOK8IoBvDIv5OMoxqwtvr4RZQqO9CZQcgtlHOAYNMtX
> zhh+r/1B27vFXoGva065AKIyGPbQSeUJesfVxwN9+RbWplWusaqLPuwfbyNttacf
> mkkNrudQ9g4=
> =yqur
> -----END PGP SIGNATURE-----
> 
> tag arm64-for-linus
> Tagger: Arnd Bergmann <arnd@arndb.de>
> Date:   Tue Dec 9 16:32:04 2014 +0100
> 
> ARM64: SoC changes for 3.19
> 
> This adds support for two new ARM64 platforms:
> 
> * ARM Juno
> * AMD Seattle
> 
> We had submissions for a number of additional platforms
> from Samsung, Freescale and Spreadtrum but are still working
> out the best process for getting these merged.
> 70bcc9b arm64: amd-seattle: Fix PCI bus range due to SMMU limitation

and both have the same text in them, which is not what I had expected.

	Arnd

  reply	other threads:[~2014-12-10 11:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 21:20 [GIT PULL 0/9] ARM: SoC changes for 3.19 Arnd Bergmann
2014-12-09 21:22 ` [GIT PULL 1/9] ARM: SoC non-critical bug fixes " Arnd Bergmann
2014-12-09 21:23 ` [GIT PULL 2/9] ARM: SoC cleanup on mach-at91 " Arnd Bergmann
2014-12-09 21:30 ` [GIT PULL 3/9] ARM: SoC cleanups " Arnd Bergmann
2014-12-09 21:34 ` [GIT PULL 4/9] ARM: SoC platform changes " Arnd Bergmann
2014-12-09 21:36 ` [GIT PULL 5/9] ARM: SoC driver updates " Arnd Bergmann
2014-12-09 21:40 ` [GIT PULL 6/9] ARM: SoC DT " Arnd Bergmann
2014-12-09 23:45   ` Linus Torvalds
2014-12-10  0:56     ` Linus Torvalds
2014-12-10 10:02     ` Arnd Bergmann
2014-12-09 21:42 ` [GIT PULL 7/9] ARM: SoC/OMAP GPMC driver cleanup and move " Arnd Bergmann
2014-12-09 21:43 ` [GIT PULL 8/9] ARM: SoC defconfig changes " Arnd Bergmann
2014-12-10  8:56   ` Geert Uytterhoeven
2014-12-10 11:16     ` Arnd Bergmann [this message]
2014-12-09 21:46 ` [GIT PULL 9/9] ARM64: SoC " Arnd Bergmann
2014-12-10  1:20   ` Linus Torvalds
2014-12-10 11:33     ` Arnd Bergmann

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=2480052.Mq2bie8eJI@wuerfel \
    --to=arnd@arndb.de \
    --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).