Castedo Ellerman

OK, sounds like you're going for "hostname" a bit in the spirit of web servers handling multiple different hostnames for different websites even though they all have the same IP...

This reminds me, here are three observation that might be of interest. 1) When podman creates a container that is not sharing the network, by default it changes the hostname...

> > perhaps there is some sense in setting the hostname to something longer, like `container-name.thehost-hostname` so that `/etc/hostname` > > I like this idea, I'll fiddle with it these...

> Right now distrobox uses the container's name as hostname for the box Just the container name alone or 'container-name.thehost-hostname'?

@89luca89 This is what I have been dogfooding for a long time now: https://github.com/castedo/cnest/blob/beb989f00d5051975b35f98b4709ac255cc21cbd/bin/create-nest#L52-L54 So far it's been working fine for me. But I might just be lucky and not...

Oh bummer. Us doing 'container_name.host_hostname' is kind of a hack. I'm not surprised it has confused some software somewhere. I've managed to not hit this problem because over the years...

Good to know, thank for looking into! I was wondering how printstrap should handle this issue.

Here's some rough thoughts I can throw out here. One decision fork is whether to represent git-tree-in-git-db and subdir-in-git-index as separate classes or some binary runtime state that git.Tree can...

Good point about the name and file mode in the git db. That makes more sense to return that extra entry information in addition to the git db tree/blob. You...

> I'd think of it as `git.objects.tree.Entry` :+1: > ```python > a = repo.head.commit.tree.entry('1/a') # access to any entry with implicit tree traversal > a.name == "a" # true >...