It fails telling me there is no this commit or tag.

git tag shows
client_release/7.0/7.0.1
client_release/7.0/7.0.10
client_release/7.0/7.0.11
client_release/7.0/7.0.12
client_release/7.0/7.0.13
client_release/7.0/7.0.14
client_release/7.0/7.0.15
client_release/7.0/7.0.16
client_release/7.0/7.0.17
client_release/7.0/7.0.18
client_release/7.0/7.0.19
client_release/7.0/7.0.2
client_release/7.0/7.0.20
client_release/7.0/7.0.21
client_release/7.0/7.0.22
client_release/7.0/7.0.23
client_release/7.0/7.0.24
client_release/7.0/7.0.25
client_release/7.0/7.0.26
client_release/7.0/7.0.27
client_release/7.0/7.0.28
client_release/7.0/7.0.29
client_release/7.0/7.0.3
client_release/7.0/7.0.30
client_release/7.0/7.0.31
client_release/7.0/7.0.32
client_release/7.0/7.0.33
client_release/7.0/7.0.34
client_release/7.0/7.0.35
client_release/7.0/7.0.36
client_release/7.0/7.0.5
client_release/7.0/7.0.6
client_release/7.0/7.0.7
client_release/7.0/7.0.8
client_release/7.0/7.0.9


the same as bash_completion


Gianfranco



>________________________________
> Da: Oliver Bock <[email protected]>
>A: Gianfranco Costamagna <[email protected]> 
>Cc: "[email protected]" <[email protected]>; Boinc 
><[email protected]> 
>Inviato: Lunedì 25 Marzo 2013 18:20
>Oggetto: Re: [boinc_dev] boinc-v2 broken?
> 
>Hi,
>
>On 3/25/13 17:08 , Gianfranco Costamagna wrote:
>> git archive --worktree-attributes  -v --format tgz -o 
>> ../boinc_7.0.58+dfsg.orig.tar.gz -9 --prefix boinc-7.0.58+dfsg/ 
>> client_release/7.0/7.0.58
>> 
>> but it FAILED.
>
>How did it fail?
>
>> locutus@Unimatrix02-Quantal:~/branches/boinc-v2 [master] $ git checkout 
>> client_release/7.0/7.0.
>> client_release/7.0/7.0.1    client_release/7.0/7.0.16   
>> client_release/7.0/7.0.22   client_release/7.0/7.0.29   
>> client_release/7.0/7.0.35 
>> client_release/7.0/7.0.10   client_release/7.0/7.0.17   
>> client_release/7.0/7.0.23   client_release/7.0/7.0.3    
>> client_release/7.0/7.0.36 
>> client_release/7.0/7.0.11   client_release/7.0/7.0.18   
>> client_release/7.0/7.0.24   client_release/7.0/7.0.30   
>> client_release/7.0/7.0.5 
>> client_release/7.0/7.0.12   client_release/7.0/7.0.19   
>> client_release/7.0/7.0.25   client_release/7.0/7.0.31   
>> client_release/7.0/7.0.6 
>> client_release/7.0/7.0.13   client_release/7.0/7.0.2    
>> client_release/7.0/7.0.26   client_release/7.0/7.0.32   
>> client_release/7.0/7.0.7 
>> client_release/7.0/7.0.14   client_release/7.0/7.0.20   
>> client_release/7.0/7.0.27   client_release/7.0/7.0.33   
>> client_release/7.0/7.0.8 
>> client_release/7.0/7.0.15   client_release/7.0/7.0.21   
>> client_release/7.0/7.0.28   client_release/7.0/7.0.34   
>> client_release/7.0/7.0.9 
>> 
>> why tags >= .36 aren't listed?
>> I can see them in gitweb, is this a bug in git?
>
>It seems you use bash-completion to view the available tags. Maybe it
>truncates the available options at some point? If you want to list all
>tags just run "git tag".
>
>
>Cheers,
>Oliver
>
>
>
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to