also sprach Uwe Kleine-König <[email protected]> [2009.03.05.1701 +0100]: > > It would be better if pristine-tar kept its trees referenced from > > e.g. refs/pristine-tar/1.2 or the like. > At first I considered using a branch being strange. For me something > tag-like seems more natural. I think this is what martin suggests here > by having the version as part of the ref, too?!
As far as I understand it, any file in refs/* is just a pointer to a commit ID. refs/heads/* are branches by convention, and git-commit has logic to advance them. refs/tags/* has tags. Stuff in refs/pristine-tar/* would essentially be the same as tags, but not processed by git-tag, but by something else: pristine-tar. also sprach Joey Hess <[email protected]> [2009.03.05.1909 +0100]: > > It would be better if pristine-tar kept its trees referenced > > from e.g. refs/pristine-tar/1.2 or the like. > > I tried, as an experiment, removing refs/heads/pristine-tar and > running gitk --all. > > The pristine-tar branch still showed up because of > refs/remotes/origin/pristine-tar. Which can't be done away with > AFAICS. Not really, since it's remote and may be cloned by others. However, a migration script could get rid of it (git push origin :pristine-tar) and it would stay gone, unless someone else pushed the ref back. As such, a migration like I am proposing has to be a concerted effort, although mistakes only have cosmetic effects. Obviously, once a project switched to the new approach, anyone using an old pristine-tar (those who would be pushing the ref back) are left out in the cold and will have to switch sooner or later anyway. > (Also, if it did put it in refs/pristine-tar, would the branch be > automatically pushed to origin by 'git push' as it is now?) No. But you could easily auto-configure that. E.g. TopGit adds the following to config.remote.origin when you use it first: fetch = +refs/top-bases/*:refs/remotes/origin/top-bases/* push = +refs/top-bases/*:refs/top-bases/* rather straight forward, and if you look at the default settings in config.remote.origin for any repo, it'll be obvious too. -- .''`. martin f. krafft <[email protected]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems gentoo: the performance placebo.
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
