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

Re: [RFH] GSoC 2015 application

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 5, 2015, 06:19 UTC
Message-ID
<xmqqsidk3r17.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAGZ79kZzB8-r2a4VGG23GL1ZqxY7c34391vMwVr09MnCV6Hqcg@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
> I cannot remember the usual option off hand to describe the revision
> instead of a date.

Because "log --since=<date of v1.0> master" and "log v1.0..master" mean two completely different things, we need some way to specify which one of these two the user wants to "git clone" so that the user can say at what point the user wants the shallow history to begin.

I think it is a good idea to use --since for date-based cut-off, in addition to the existing --depth that is depth-based cut-off, and we probably would want another one that gives the topology-based cut-off, so that we can express the range in a similar way to "log v1.0..master".

But when we talk about the topology-based cut-off locally, we always use the set syntax A..B, ^A B, etc. and never a command line option with an argument to specify "the bottom of the history". It is not surprising that you don't remember any usual option for that, because there isn't one.

The closest thing I can think of that looks somewhat like a command line option is "--not", as in

    git log A B --not C D E

that is equivalent to "A B ^C ^D ^E", but that is not an option that takes an argument. I do not know if it is particularly a good idea to say:

    git clone --not v2.0 $URL
to specify topology-based cut-off.

But we would need some way to say a set-based cut-off; I do not think using --since for that purpose is a good idea, though, because that is already taken for date-based cut-off, and mixing them together will introduce confusion.

Previous: Junio C HamanoNext: Duy Nguyen
Message 62 of 74 in “[RFH] GSoC 2015 application”
  1. Jeff KingFeb 18, 2015
  2. Jeff KingFeb 18, 2015
  3. Johannes SchindelinFeb 24, 2015
  4. Jeff KingFeb 24, 2015
  5. Johannes SchindelinFeb 24, 2015
  6. Jeff KingFeb 24, 2015
  7. Johannes SchindelinFeb 25, 2015
  8. Matthieu MoyFeb 25, 2015
  9. Matthieu MoyFeb 25, 2015
  10. Johannes SchindelinFeb 25, 2015
  11. Matthieu MoyFeb 24, 2015
  12. Junio C HamanoFeb 24, 2015
  13. Johannes SchindelinFeb 24, 2015
  14. Junio C HamanoFeb 24, 2015
  15. Matthieu MoyFeb 24, 2015
  16. Stefan BellerFeb 25, 2015
  17. Michael J GruberFeb 25, 2015
  18. Johannes SchindelinFeb 25, 2015
  19. Christian CouderFeb 25, 2015
  20. Duy NguyenFeb 25, 2015
  21. Johannes SchindelinFeb 25, 2015
  22. Junio C HamanoFeb 18, 2015
  23. Junio C HamanoFeb 19, 2015
  24. Matthieu MoyFeb 19, 2015
  25. Jeff KingFeb 20, 2015
  26. Matthieu MoyFeb 20, 2015
  27. Dennis KaarsemakerFeb 20, 2015
  28. Matthieu MoyFeb 20, 2015
  29. Eric SunshineFeb 20, 2015
  30. 1/3 microprojects: tweaks after discussion with PeffMatthieu Moy, Feb 20, 2015
  31. 2/3 GSoC ideas: git bisect fixed/unfixedMatthieu Moy, Feb 20, 2015
  32. 3/3 idea: Be nicer to the user on tracked/untracked merge conflictsMatthieu Moy, Feb 20, 2015
  33. Duy NguyenFeb 20, 2015
  34. Jeff KingFeb 20, 2015
  35. Junio C HamanoFeb 20, 2015
  36. Support customized reordering in version sortDuy Nguyen, Feb 21, 2015
  37. Junio C HamanoFeb 21, 2015
  38. Duy NguyenFeb 21, 2015
  39. Junio C HamanoFeb 21, 2015
  40. Junio C HamanoFeb 21, 2015
  41. versionsort: support reorder prerelease suffixesNguyễn Thái Ngọc Duy, Feb 26, 2015
  42. Junio C HamanoFeb 27, 2015
  43. Junio C HamanoMar 5, 2015
  44. Duy NguyenMar 9, 2015
  45. Junio C HamanoMar 10, 2015
  46. Eric SunshineMar 10, 2015
  47. config.txt: update versioncmp.prereleaseSuffixNguyễn Thái Ngọc Duy, Mar 10, 2015
  48. Michael HaggertyFeb 20, 2015
  49. Jeff KingFeb 20, 2015
  50. Junio C HamanoFeb 20, 2015
  51. Matthieu MoyFeb 20, 2015
  52. Jeff KingFeb 20, 2015
  53. Jeff KingFeb 20, 2015
  54. Matthieu MoyFeb 23, 2015
  55. Jeff KingFeb 23, 2015
  56. Philip OakleyMar 4, 2015
  57. Stefan BellerMar 4, 2015
  58. Philip OakleyMar 4, 2015
  59. Junio C HamanoMar 5, 2015
  60. Stefan BellerMar 5, 2015
  61. Junio C HamanoMar 5, 2015
  62. Junio C HamanoMar 5, 2015
  63. Duy NguyenMar 6, 2015
  64. Duy NguyenMar 5, 2015
  65. Nguyễn Thái Ngọc DuyMar 5, 2015
  66. 1/6 upload-pack: move shallow deepen code out of receive_needs()Nguyễn Thái Ngọc Duy, Mar 5, 2015
  67. 2/6 upload-pack: move "shallow" sending code out of deepen()Nguyễn Thái Ngọc Duy, Mar 5, 2015
  68. 3/6 upload-pack: remove unused variable "backup"Nguyễn Thái Ngọc Duy, Mar 5, 2015
  69. 4/6 upload-pack: move "unshallow" sending code out of deepen()Nguyễn Thái Ngọc Duy, Mar 5, 2015
  70. 5/6 shallow.c: implement a generic shallow boundary finder based on rev-listNguyễn Thái Ngọc Duy, Mar 5, 2015
  71. 6/6 upload-pack: example code to use get_shallow_commits_by_rev_listNguyễn Thái Ngọc Duy, Mar 5, 2015
  72. Duy NguyenFeb 26, 2015
  73. Jeff KingMar 4, 2015
  74. Duy NguyenMar 4, 2015

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.