On 01/02/2008, Joey Hess wrote: > Applied, except I don't like pristine-tar prompting, I think it should > be something that can be run noninteractively. So I removed that part > and made it just use the remote branch if there was exactly one.
OK, it works fine out of the box… (right after a git-clone) until you tell git to track the remote branch: | [EMAIL PROTECTED]:~/pristine-tar-debug$ git-branch -D pristine-tar | Deleted branch pristine-tar. | [EMAIL PROTECTED]:~/pristine-tar-debug$ git-branch -a | * upstream | origin/HEAD | origin/pristine-tar | origin/upstream | [EMAIL PROTECTED]:~/pristine-tar-debug$ pristine-tar checkout ../graphviz_2.16.1.orig.tar.gz | pristine-tar: successfully generated ../graphviz_2.16.1.orig.tar.gz | [EMAIL PROTECTED]:~/pristine-tar-debug$ git-branch pristine-tar origin/pristine-tar | Branch pristine-tar set up to track remote branch refs/remotes/origin/pristine-tar. | [EMAIL PROTECTED]:~/pristine-tar-debug$ pristine-tar checkout ../graphviz_2.16.1.orig.tar.gz | pristine-tar: Several remote pristine-tar branches exist. Run "git branch --track pristine-tar <remote>" to create a local pristine-tar branch | 47c7239a30438f24785ab96f2b38db5e92b73d7b refs/heads/pristine-tar | 47c7239a30438f24785ab96f2b38db5e92b73d7b refs/remotes/origin/pristine-tar A bit confusing. What about using the same kind of SHA1 detection as done for the upstream branch? The local pristine-tar branch would take precedence, and a remote pristine-tar would be a fallback. I'm (only) forwarding this request from someone would gave pristine-tar a try: please add an end-of-line to the .id files (so that they can be cat'd). bzip2 support is being tested, but looks quite OK until now. I'm cleaning my patches and pushing that quite soon. -- Cyril Brulebois
pgpdSrxiVpYuG.pgp
Description: PGP signature
