lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 23 May 2012 09:41:13 -0700 From: Tony Luck <tony.luck@...il.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: [GIT PULL] PCI updates for 3.5 merge window On Mon, May 21, 2012 at 4:26 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > Looks fine, except please actually mention the tag itself on the repo > pull line. IOW, not like this: > >> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next > > but simply > > git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-for-3.5 git request-pull seems to look for branches before tags when generating this text. It just did exactly the same thing for me (since the tag I created also pointed to my "next" branch). This would seem to be the common case for people following the rules and sending you stuff in the merge window that they have had cooking in linux-next. Can "request-pull" be smarter - or is their some magic I should be using on the "git request-pull" command line that will tell it that I really mean the tag and not the branch? Or is "smarter" already in a newer version of git - I have: $ git --version git version 1.7.9.5 -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists