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-c
Cyril Brulebois wrote:
> I'm also wondering whether it would be nice to catch missing local
> “pristine-tar” local branch.
>
> Currently, if git-branch is omitted above, one ends up getting:
> | $ pristine-tar checkout ../graphviz_2.16.orig.tar.gz
> | fatal: ambiguous argument 'pristine-tar:graphv
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.
Sure, I thought so, that's why I didn't add any code but only suggested
the idea anyway.
--
Cyril Brulebois
pgpqdncZCiLPq.pgp
Description: P
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.de
Cyril Brulebois <[EMAIL PROTECTED]> (01/02/2008):
> -- 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 checkout ../graphviz_2.16.orig.tar.gz # obviously
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
6 matches
Mail list logo
