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

Re: [PATCH] revision: add --except option

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Sep 2, 2013, 06:25 UTC
Message-ID
<52242F61.3090404@viscovery.net>
In-Reply-To
<CAMP44s0D98tggTjQsMn+-03KgSsbrh3nxYfLofpC1gfnJpEPyw@mail.gmail.com>
Am 8/31/2013 21:27, schrieb Felipe Contreras:
Show 48 quoted lines
> On Fri, Aug 30, 2013 at 2:56 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>> Am 8/30/2013 8:32, schrieb Junio C Hamano:
>>> If you have a history where
>>>
>>>  - branches "master" and "maint" point at commit A;
>>>  - branch "next" points at commit B that is a descendant of A; and
>>>  - there are tags X and Y pointing at commits that are ahead of B
>>>    or behind A
>>>
>>> i.e.
>>>
>>>       ----X----A----B----Y
>>>
>>> what are the desired semantics for these?
>>
>> I think the simplest were that --except trumps everything and means
>> "whatever else I say, do as if I did not mention the following".
> 
> Actually, my patch is almost there, I attach the necessary changed
> below to make everything work. I've added debug prints to show what
> it's actually doing:
> 
>>>  (1) --branches --except maint
>>
>> => master next
> 
> => master next
> 
>>>  (2) --all --not --branches --except maint
>>
>> => X Y --not master next
> 
> => ^master ^next X Y HEAD
> 
>>>  (3) ^master next --except maint
>>
>> => ^master next
> 
> => ^master next
> 
>> (4) Y next --except master next --not --branches
>>
>> this => Y --not maint
>> or this => Y --not maint master next
> 
> => Y
> 
> Remember that maint (or rather ^maint) is after --except.

Sure, but why is it not in the result? maint is not even mentioned under --except. Confused...

Ah, are you treating the union of master, next, and --branches as --except and ignore --not?

-- Hannes
Previous: Felipe ContrerasNext: Felipe Contreras
Message 7 of 32 in “revision: add --except option”
  1. revision: add --except optionFelipe Contreras, Aug 30, 2013
  2. Felipe ContrerasAug 30, 2013
  3. Junio C HamanoAug 30, 2013
  4. Felipe ContrerasAug 30, 2013
  5. Johannes SixtAug 30, 2013
  6. Felipe ContrerasAug 31, 2013
  7. Johannes SixtSep 2, 2013
  8. Felipe ContrerasSep 2, 2013
  9. Johannes SixtAug 30, 2013
  10. Felipe ContrerasAug 30, 2013
  11. Felipe ContrerasAug 30, 2013
  12. Johannes SixtAug 30, 2013
  13. Junio C HamanoAug 30, 2013
  14. Felipe ContrerasAug 30, 2013
  15. revision: introduce --exclude=<glob> to tame wildcardsJunio C Hamano, Aug 30, 2013
  16. Duy NguyenAug 31, 2013
  17. Junio C HamanoAug 31, 2013
  18. Felipe ContrerasAug 31, 2013
  19. Junio C HamanoSep 3, 2013
  20. Felipe ContrerasSep 3, 2013
  21. Johannes SixtSep 2, 2013
  22. Felipe ContrerasSep 2, 2013
  23. Michael HaggertySep 3, 2013
  24. Junio C HamanoSep 3, 2013
  25. Johannes SixtSep 3, 2013
  26. 0/5 ref glob exclusion follow-upJunio C Hamano, Nov 1, 2013
  27. 3/5 rev-list --exclude: testsJunio C Hamano, Nov 1, 2013
  28. 4/5 rev-list --exclude: export add/clear-ref-exclusion and ref-excluded APIJunio C Hamano, Nov 1, 2013
  29. 5/5 rev-parse: introduce --exclude=<glob> to tame wildcardsJunio C Hamano, Nov 1, 2013
  30. Eric SunshineNov 1, 2013
  31. Junio C HamanoNov 1, 2013
  32. Johannes SixtNov 1, 2013

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.