That works. Thank you, Pedro. On Thu, Sep 23, 2021 at 11:36 PM Pedro Henrique Exenberger Becker < pe...@ac.upc.edu> wrote:
> You can try `git commit -m "my message" - n` > > -n is the short version of - -no-verify flag. > https://git-scm.com/docs/git-commit > > However your commits won't be compliant with gem5 standards. I guess this > can be a problem if you want to push your code/modifications to the main > repo some day, but I'm not sure. > > Pedro. > > Em sex, 24 de set de 2021 07:48, Todd Bezenek via gem5-users < > gem5-users@gem5.org> escreveu: > >> (Please be sure to look at my question at the bottom of this message. >> Also, please excuse the length of the message--I want it to be complete.) >> >> You were assigned to review my first Gem5 check-in, so you are getting >> this annoying email. I'm sorry about that, but I do not know who would be a >> better person. :) >> >> In order to satisfy the requirements for a proper Gem5 check-in, I had to >> do a couple of things that changed the way git works on my machine. As a >> result, when I do a "git commit" on a different repository from the >> machine, the required background stuff for Gem5 is launching. How do I turn >> this off? >> >> The problem is likely because I am creating my own local Gem5 repository >> to play with on the same machine that has the repository I used to create >> the reviewable check-in. Now when I try to do a commit to the "play with" >> repository, the script which helps to set up the Gem5 reviewable check-in >> launches and I get this message: >> ----- >> toddb@zippy $ git commit -m "After my change was sent to Gem5." >> Invalid commit header >> The commit has been cancelled, but a copy of it can be found in >> .git/COMMIT_EDITMSG : >> >> -------------------------------------------------------------------------- >> >> After my change was sent to Gem5. >> >> Change-Id: I8f1ef29ab9af589bf433806b5483571728bb0998 >> >> >> -------------------------------------------------------------------------- >> >> >> The first line of a commit must contain one or more gem5 tags separated by >> commas (see MAINTAINERS.yaml for the possible tags), followed by a colon >> and >> a commit title. There must be no leading nor trailing whitespaces. >> >> This header line must then be followed by an empty line. A detailed >> message, >> although highly recommended, is not mandatory and can follow that empty >> line. >> >> e.g.: >> cpu: Refactor branch predictors >> >> Refactor branch predictor code to improve its readability, moving >> functions >> X and Y to the base class... >> >> e.g.: >> mem,mem-cache: Improve packet class readability >> >> The packet class... >> >> Thu Sep 23 08:38:17 ~/Work/Gem5 >> ----- >> >> My question is, how do I get rid of whatever is happening in the >> background for this other repository on the same machine where the repo I >> have for reviewable check-ins is? >> >> If you cannot answer this easily, I will spend more time trying to figure >> it out myself. >> >> Thank you for your patience. The first check-in is always troublesome. :) >> >> -Todd >> _______________________________________________ >> gem5-users mailing list -- gem5-users@gem5.org >> To unsubscribe send an email to gem5-users-le...@gem5.org >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
