On Tue, Feb 02, 2021 at 01:03:23PM +0000, Robie Basak wrote: > What goes into the changes file is three fields. Example: > https://launchpadlibrarian.net/516799033/hello_2.10-2ubuntu3~ppa1_source.changes > > Vcs-Git: https://git.launchpad.net/~racb/ubuntu/+source/hello > Vcs-Git-Commit: 4511fdfc01cbfd5bc351e1da294d6acb44e8a4a2 > Vcs-Git-Refs: refs/heads/test > > We need the Refs field because git is designed not to be able to fetch a > commit by hash, but by a ref that can reach it only. So Vcs-Git-Refs > must specify what ref(s), when fetched will make the commit given to be > reachable. In practice this could just be the branch name prefixed by > 'refs/heads/' as in this example.
I don't buy this argument. A ref is just a file containing the commit name, it doesn't matter to git. And here's the proof that fetching by id just works: $ git init c1 Initialized empty Git repository in /home/jak/Projects/Debian/c1/.git/ $ cd c1 $ git remote add origin ../command-not-found $ git fetch origin f5c1bf45c86d0c91382b289ef780016722ea8efa remote: Enumerating objects: 448, done. remote: Counting objects: 100% (448/448), done. remote: Compressing objects: 100% (390/390), done. remote: Total 448 (delta 132), reused 0 (delta 0), pack-reused 0 Receiving objects: 100% (448/448), 2.34 MiB | 6.53 MiB/s, done. Resolving deltas: 100% (132/132), done. From ../command-not-found * branch f5c1bf45c86d0c91382b289ef780016722ea8efa -> * FETCH_HEAD -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
signature.asc
Description: PGP signature
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
