Re: Repository edit
On 19.07.23 04:30, Gedare Bloom wrote: I had a local copy of the two commits that were dropped during the rewinding. I have pushed them back. We are back to the state prior to the accidental push. Hashes all look good. Thanks for handling this. Thanks, looks good. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Repository edit
I had a local copy of the two commits that were dropped during the rewinding. I have pushed them back. We are back to the state prior to the accidental push. Hashes all look good. Thanks for handling this. Gedare On Tue, Jul 18, 2023 at 7:55 PM Amar Takhar wrote: > > There was a mistaken push to the RTEMS main repository earlier. These things > happen so we have rewound the repository back to the latest safe commit. > > This is 1425735. > > If anyone did checkout the repository afterwards they will get an error when > trying to update as the repository has been rewound. You can solve this by > doing a fresh clone -- something I always recommend > > Alternatively you can reset your own repository by doing > > git reset --hard 1425735 > > While on the master branch -- please keep in mind this will blow away any > changes you have in your source tree. > > Sebastian, I noticed you had two commits pushed after these will need to be > re-applied as rewinding back is the safest and best way to handle this. > > > Amar. > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Repository edit
There was a mistaken push to the RTEMS main repository earlier. These things happen so we have rewound the repository back to the latest safe commit. This is 1425735. If anyone did checkout the repository afterwards they will get an error when trying to update as the repository has been rewound. You can solve this by doing a fresh clone -- something I always recommend Alternatively you can reset your own repository by doing git reset --hard 1425735 While on the master branch -- please keep in mind this will blow away any changes you have in your source tree. Sebastian, I noticed you had two commits pushed after these will need to be re-applied as rewinding back is the safest and best way to handle this. Amar. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
