cgit: orientation

Mark Millard marklmi at
Wed Feb 10 21:53:17 UTC 2021

On 2021-Feb-10, at 12:19, Graham Perrin <grahamperrin at> wrote:

> On 10/02/2021 15:46, Rodney W. Grimes wrote:
>>> On Tue, Feb 9, 2021 at 5:52 PM Warner Losh <imp at> wrote:
>>>> On Tue, Feb 9, 2021 at 5:47 PM Graham Perrin <grahamperrin at>
>>>> wrote:
>>>>> Given this, for example:
>>>>> <
>> This link probably came from someone copying it out of the address bar
>> from some browswer, the better way to get a link out of a cgit page
>> is to copy it from the commit: hash line that looks like:
>> 	commit 174a7e578a33c01401e33f9bfcc077fc3155251c (patch)
>> Right click on the hash and select copy link location.
> Thanks, I already tried that. Result: again, 'stable' in the URL and 'stable/12' visible in the page.
> (It was me who originally copied the URL, to demonstrate what can happen if someone else does so.)
> Please check my sanity. Is it true that this particular commit is _not_ in stable/12?

It is in main. My exploration was as follows but the
general behavior is odd to me.

Finding where the commit is from for sure . . .

Using the id in a range search still says main and lists:

Commit message (Expand)	Author	Age	Files	Lines
* 	ZFS: fix assertions with INVARIANTS	Alan Somers	45 hours	1	-0/+2
* 	Revert "SO_RERROR indicates that receive buffer overflows should be handled a...	Alexander V. Chernikov	47 hours	21	-100/+35
* 	hid: bump HID_ITEM_MAXUSAGES to 8	Warner Losh	47 hours	1	-1/+1
* 	Don't check compat.linux.emul_path before loading linux(4)	Edward Tomasz Napierala	47 hours	1	-1/+3
* 	acpi: limit the AMDI0020/AMDI0010 workaround to an option	Warner Losh	47 hours	2	-0/+4
* 	Turn off forgotten multipath debug messages	Alexander V. Chernikov	47 hours	1	-1/+0

Going to does not list those.

Going to does not list those.

Going to does list those.

So: main.

Exploring using search to find the commit . . .

If one starts at: and does a rnage
search for the id of a stable/12 commit the URL ends up being:

The upper right ends up showing main , not stable/12 .
The commit message links also do not specify the branch, for
example (copy/pasted):

The next link is (copy/pasted):

Using it again leaves main in the upper right.

It appears that first going to
and using links there or using a stable/12 link that happens to
be on the page for is required to get the
branch tracking started --and you have to avoid operations like
range search that drop that tracking (in what is explicitly

Just having an id and trying to use it is insufficient context
for to identify branches overall.

(I do not claim that the "?h=stable/12" notation is completely
unique to the purpose. For example the original reports'
"&h=stable%2F12" can be generated. I'll ignore the variable
notation generally, just showing what I did got as text.)

I also explored some what URL's to a stable/12 commit would do

The one without "?h=stable/12&" indicates main in the upper right
and copy/paste of the commit link shown also does *not* include
"?h=stable/12&" text. Further activity from there continues to
not have the text.

Of course, if one goes back through one of, say,

one ends up in a context that supplies the "?h=stable/12&".

Repeating with the one that has "?h=stable/12&" shows stable/12
in the upper right and copy/ptase of the commit link show does
include "?h=stable/12&" text. Further activity from there
continues to have the text.

Of course if one does a range search for the id, the context
is lost.

Summary: if you want do see what branch via
use you have to use in very specific ways.

Mark Millard
marklmi at
( went
away in early 2018-Mar)

More information about the freebsd-git mailing list