[petsc-dev] [petsc-maint] Who fucked up the repository?

Jed Brown jedbrown at mcs.anl.gov
Sun Jun 16 14:19:21 CDT 2013


Matthew Knepley <knepley at gmail.com> writes:

> On Sat, Jun 15, 2013 at 10:44 PM, Karl Rupp <rupp at mcs.anl.gov> wrote:
>
>> Hey,
>>
>>
>>  1) I ran the push again, even after issuing the command above, and still
>>> got the same error
>>>
>> >
>> > 2) How do I update my copy of 3.4.1? I pulled every branch and did a
>> fetch.
>> >
>>
>> Did you try `git pull --tags` and/or `git fetch --tags`?
>>
>
> Yes, that worked. I cannot understand why this tag was different from all
> the others.

Satish explained this in the other mail.  We should use annotated
(preferably signed) tags for release tags since it makes 'git describe'
do the right thing without options and because it makes it faster to
"check" tags in another clone of PETSc (versus manually comparing SHA1).



More information about the petsc-dev mailing list