git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: sparse support in pu

From
PHPeter Harris <git@peter.is-a-geek.org>
Date
Aug 17, 2009, 12:52 UTC
Message-ID
<eaa105840908170552m3eaf0f92j523ddad98dd67a3@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0908171425410.4991@intel-tinevez-2-302>
On Mon, Aug 17, 2009 at 8:29 AM, Johannes Schindelin wrote:
> If I want to have a sparse checkout, I know which files I _want_.

That's funny. I have a git tree that would benefit from sparse checkout. I know which path I _don't_ want. Specifying all the paths I want would be a rather longer (and more error-prone) list. I suspect it would be best to support both.

Does sparse use the same parser as .gitignore? (I guess not, if it handles trailing slashes differently?) If so, it would be trivial to turn "exclude path" into "exclude all but path" (or vice-versa) with:

* !path

Peter Harris
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 15 of 21 in “sparse support in pu”
  1. skillzero@gmail.comAug 17, 2009
  2. Nguyen Thai Ngoc DuyAug 17, 2009
  3. skillzero@gmail.comAug 17, 2009
  4. Johannes SchindelinAug 17, 2009
  5. skillzero@gmail.comAug 17, 2009
  6. Johannes SixtAug 17, 2009
  7. Johannes SchindelinAug 17, 2009
  8. Nguyen Thai Ngoc DuyAug 17, 2009
  9. Nguyen Thai Ngoc DuyAug 17, 2009
  10. Johannes SixtAug 17, 2009
  11. Nguyen Thai Ngoc DuyAug 17, 2009
  12. Johannes SixtAug 17, 2009
  13. Nguyen Thai Ngoc DuyAug 17, 2009
  14. Johannes SchindelinAug 17, 2009
  15. Peter HarrisAug 17, 2009
  16. Johannes SchindelinAug 17, 2009
  17. Peter HarrisAug 17, 2009
  18. Junio C HamanoAug 17, 2009
  19. Johannes SchindelinAug 17, 2009
  20. Nguyen Thai Ngoc DuyAug 17, 2009
  21. James PickensAug 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.