Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

[avih]

While force-pushing is usually possible, I'd argue that at the tcc repo
(and generally elsewhere too, but to each his own practices) no one
should force push except maybe maintainers and maybe other regular
contributors which 100% know what they're doing when force-pushing.

I.e. if you want something reverted at the mob repo, please ask here
at the mailing list and one of the regulars will judge how to handle
the request, IMHO.

- avih

On Friday, September 11, 2020, 09:29:29 PM GMT+3, Patrick Hammer <patham9@gmail.com> wrote:

Hi!

Force pushing is dangerous, make sure to have a copy of the repo backed up!

Sometimes it's necessary though. If you need to do it, make sure that each developer re-clones the repository!

I had to do it yesterday for https://github.com/opennars/opennars-for-applications

as one author pushed with a wrong email address, and this demands a rebase&amend, which changes all commit hashes beginning from the edited commit.

Best regards,

Patrick

Am Fr., 11. Sept. 2020 um 17:25 Uhr schrieb Pursuer <1596067968@qq.com>:

I found a way to remove these empty commit, by use "git rebase -i".  But I can't push these change without -f flag, and I have been told that do NOT use "git push -f". So I can only give up to revert it.

------------------ Original ------------------

From: "tinycc-devel" <tinycc-devel@nongnu.org>;

Date: Fri, Sep 11, 2020 11:35 PM

To: "tinycc-devel"<tinycc-devel@nongnu.org>;

Cc: "Larry Doolittle"<ldoolitt@recycle.lbl.gov>;

Subject: Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

Pursuer -

On Fri, Sep 11, 2020 at 11:27:05PM +0800, Pursuer wrote:
> I'm sorry that I pull code in wrong way.&nbsp;
> And now there are many commit like&nbsp;
> Merge branch 'mob' of git://repo.or.cz/tinycc into mob
> How can I remove them.

Obligatory xkcd:
https://xkcd.com/1597/

There are fancier (and arguably more efficient) ways to recover than
"delete the project, and download a fresh copy".
But they're harder to explain and understand.

  - Larry

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel