Search Options

Results per page
Sort
Preferred Languages
Advance

Results 641 - 650 of 787 for field11 (0.06 sec)

  1. licenses/sigs.k8s.io/kustomize/api/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Thu Apr 22 22:59:25 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  2. licenses/sigs.k8s.io/mcs-api/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Fri Mar 12 21:17:55 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  3. licenses/sigs.k8s.io/structured-merge-diff/v4/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sun Aug 30 14:15:49 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  4. licenses/github.com/docker/distribution/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  5. licenses/github.com/go-logr/stdr/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Jul 17 20:25:52 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  6. licenses/github.com/go-openapi/jsonreference/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/google/btree/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  8. src/archive/zip/zip_test.go

    		t.Skip("slow test; skipping")
    	}
    	t.Parallel()
    	// Test a zip file with uncompressed size 0xFFFFFFFF.
    	// That's the magic marker for a 64-bit file, so even though
    	// it fits in a 32-bit field we must use the 64-bit field.
    	// Go 1.5 and earlier got this wrong,
    	// writing an invalid zip file.
    	const size = 1<<32 - 1 - int64(len("END\n")) // before the "END\n" part
    	buf := testZip64(t, size)
    Registered: Tue Nov 05 11:13:11 UTC 2024
    - Last Modified: Thu May 23 01:00:11 UTC 2024
    - 19.6K bytes
    - Viewed (0)
  9. internal/config/storageclass/storage-class.go

    	return nil
    }
    
    // GetParityForSC - Returns the data and parity drive count based on storage class
    // If storage class is set using the env vars MINIO_STORAGE_CLASS_RRS and
    // MINIO_STORAGE_CLASS_STANDARD or server config fields corresponding values are
    // returned.
    //
    // -- if input storage class is empty then standard is assumed
    //
    // -- if input is RRS but RRS is not configured/initialized '-1' parity
    //
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 12 12:24:04 UTC 2024
    - 12.3K bytes
    - Viewed (0)
  10. LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Thu Oct 31 13:40:30 UTC 2024
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
Back to top