Cyril Brulebois wrote: > Package: pristine-tar > Version: 0.5 > Severity: minor > > I'm wondering whether assuming that the user wants to “pristine-tar > commit” against the local upstream branch would be nice. Here is an > example: > > ---------- o< o< o< ---------- > $ git-clone git://alioth.debian.org/~kibi-guest/pristine-tar-debug.git > # … > $ cd pristine-tar-debug > $ git-branch pristine-tar origin/pristine-tar > $ pristine-tar commit ../graphviz_2.16.orig.tar.gz > pristine-tar: more than one ref matches "upstream": > 5d23788286712f7ceda4e46f66d8c60272c1f388 refs/heads/upstream > 5d23788286712f7ceda4e46f66d8c60272c1f388 refs/remotes/origin/upstream > ---------- >o >o >o ----------
Yes, I think it makes sense to use refs/heads/upstream here. Or even to use refs/heads/upstream and fall back anything matching "upstream" if there's just one -- that way if you've checked out a clone and haven't made a local upstream branch yet, but there's a remote one, it would use that. -- see shy jo
signature.asc
Description: Digital signature
