Re: Nuking the Cygwin packaging for 'chere'

Vadim (vadcx) via Cygwin-apps wrote:
> On 8/27/25 06:30, Mark Geisert via Cygwin-apps wrote:
>
>> By mistake I replicated the author's git repository of chere into the 
>> Cygwin repository.  How can I nuke that so I can push my own repo, 
>> which just has a .cygport and patch file like most projects have?
>>
>> I suspect a 'git reset' then 'git push' on a clone of the target repo 
>> will fail because the reset would clear out the config, right?
>
> Hi, I assume you're asking for a general git advice (as in there's no 
> special handling by the cygwin git server).
>
> You can "git push --force" to completely overwrite whatever is on the 
> server. However, it is frowned upon by git folks, because once it's 
> public, it is assumed someone might've cloned it and will rely on a 
> straight history without rewrites. Result: whatever you have committed 
> locally will end up on the server. A complete replacement.
>

If upstream ('master'?) and local ('main'?) branch+tag names do not 
overlap, the new contents could be pushed to upstream as an unrelated 
branch without affecting the old contents. The upstream 'default branch' 
config needs to be changed then. The old contents could be retired later 
by deleting all old branches+tags.

I did this during the move of the upstream repo of smartmontools 
(started 2002 with cvs) from SF svn to GitHub. A custom svn2git 
conversion result with new branch names has been pushed to the existing 
svn->git R/O mirror. No problems occurred so far.

-- 
Regards,
Christian