From: Michael J Gruber <git@drmicha.warpmail.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
git@vger.kernel.org
Subject: Re: Linux 3.1-rc5
Date: Tue, 06 Sep 2011 09:23:39 +0200 [thread overview]
Message-ID: <4E65CA7B.5050803@drmicha.warpmail.net> (raw)
In-Reply-To: <4E65307F.5020103@redhat.com>
Mauro Carvalho Chehab venit, vidit, dixit 05.09.2011 22:26:
> Em 04-09-2011 20:27, Linus Torvalds escreveu:
>
>> One thing to note: If you just do
>>
>> git pull https://github.com/torvalds/linux.git
>>
>> you probably won't get the tags, since it's not your origin branch. So do
>>
>> git fetch --tags<...>
>>
>> too, so that you get not only the actual changes, but the tag that you
>> can verify too.
>>
>
> It would be great if "git remote update" could also verify the tag
> signature (if present), as most of us just do a "git remote update".
...when you should "git fetch --all" ;)
> Maybe an extra parameter for git config remote.tagopt?
>
> Ok, if in doubt, we can always use git tag -v <new tag>, but doing
> it automagically would help us to detect if a git tag got mangled
> by some at the moment we update our trees, with seems to be
> a good idea.
The update hook (if you want to reject falsified tags) or post-update
hook (if you want to be warned) is the perfect place for this. It would
be worth amending the standard update hook, me thinks, after removing
its insisting on a project description, and maybe switching the defaults.
Michael
next prev parent reply other threads:[~2011-09-06 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 23:27 Linux 3.1-rc5 Linus Torvalds
2011-09-05 1:09 ` Mithrandir
2011-09-05 4:02 ` Linus Torvalds
2011-09-05 20:26 ` Mauro Carvalho Chehab
2011-09-06 7:23 ` Michael J Gruber [this message]
2011-09-07 1:37 ` Henrique de Moraes Holschuh
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=4E65CA7B.5050803@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=torvalds@linux-foundation.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