http://www.trinitydesktop.org/patches/
Commit 7aaf58e2, 2012-08-21, was submitted by "root."
Who is root?
Darrell
Dne st 22. srpna 2012 Darrell Anderson napsal(a):
http://www.trinitydesktop.org/patches/
Commit 7aaf58e2, 2012-08-21, was submitted by "root."
Who is root?
Darrell
Not only is the 'root', but also made a mistake in submodule cmake that shifted to the older version (which was subsequently corrected by automat).
Slavek --
Dne st 22. srpna 2012 Darrell Anderson napsal(a):
http://www.trinitydesktop.org/patches/
Commit 7aaf58e2, 2012-08-21, was submitted by "root."
Who is root?
Darrell
Not only is the 'root', but also made ââa mistake in submodule cmake that shifted to the older version (which was subsequently corrected by automat).
Slavek
Whoops. That's me; I committed a minor change from a test box and forgot to set up a proper GIT user first.
I don't know if there is any way to fix this. I never really liked the fact that anyone can use any username they want when committing to GIT (as long as the proper login credentials are given), and this is a prime example of what I was concerned about.
Tim
Whoops. That's me; I committed a minor change from a test box and forgot to set up a proper GIT user first.
I don't know if there is any way to fix this. I never really liked the fact that anyone can use any username they want when committing to GIT (as long as the proper login credentials are given), and this is a prime example of what I was concerned about.
Tim
I have pushed a fix for the bad commit into GIT head. This may require that you hard reset to the latest origin/master hash to prevent problems when committing later.
Tim
Whoops. That's me; I committed a minor change from a test box and forgot to set up a proper GIT user first.
I don't know if there is any way to fix this. I never really liked the fact that anyone can use any username they want when committing to GIT (as long as the proper login credentials are given), and this is a prime example of what I was concerned about.
Tim
I have pushed a fix for the bad commit into GIT head. This may require that you hard reset to the latest origin/master hash to prevent problems when committing later.
Tim
Well, that didn't work. I don't think there is any good way to clean out the offending commit unfortunately.
Tim
Whoops. That's me; I committed a minor change from a test box and forgot to set up a proper GIT user first.
I don't know if there is any way to fix this. I never really liked the fact that anyone can use any username they want when committing to GIT (as long as the proper login credentials are given), and this is a prime example of what I was concerned about.
Tim
I have pushed a fix for the bad commit into GIT head. This may require that you hard reset to the latest origin/master hash to prevent problems when committing later.
Tim
Well, that didn't work. I don't think there is any good way to clean out the offending commit unfortunately.
Tim
OK, I was able to scrub it out but it wasn't easy. The moral of the story here is to always, always check the Author line BEFORE pushing to master!
Tim
-
Darrell Anderson -
Slávek Banko -
Timothy Pearson