commit

I would like to check for author's e-mail and name, surname to verify who's pushing to my repo. Is there any way that I can come up with a command in git to show commiter's name/e-mail given only SHA1 of the commit? This is what I came up with but it's far from ideal solution (the first solution is for git hook that's why it's using 2 SHA1s with rev-list . The second one simply uses git show ): git rev-list -n 1 --pretty=short ccd3970..6ddf170 | grep Author | cut -d ' ' -f2- | rev | cut -d ' ' -f2- | rev git show 6ddf170 | grep Author | cut -d ' ' -f2- | rev | cut -d ' ' -f2- | rev Igal S. You

MY PLATFORM: PHP & mySQL MY SITUATION: I am trying to implement transactions within my code. I tried to follow examples, but it's not much help. I am running 3 queries and I wanted to write a transaction in such a way so that if any of the query(ies) fail, the whole transaction should roll back. I would really appreciate a simple, efficient and non-object oriented PHP code to achieve this goal. Thank you in advance. MY PHP CODE: //db_res calls a custom function that performs a mysql_query on the query $res1 = db_res("SELECT c1, c2 FROM t1 WHERE c5 = 3"); $res2 = db_res("UPDATE t2 SET c1 = 5

If I want to create a table and insert a new entry in another table, can this be made atomic in the sqlite module? Refering to the docs at http://docs.python.org/2/library/sqlite3.html : By default, the sqlite3 module opens transactions implicitly before a Data Modification Language (DML) statement (i.e. INSERT/UPDATE/DELETE/REPLACE), and commits transactions implicitly before a non-DML, non-query statement (i. e. anything other than SELECT or the aforementioned). So if you are within a transaction and issue a command like CREATE TABLE ..., VACUUM, PRAGMA, the sqlite3 module will commit

Say I have a table where I want to use a serial as primary key to ask for changes from the client. The client will ask "give me the changes after key X". Without using SERIALIZABLE isolation level or locking, this is prone to race conditions. Transaction A can start first, and do its writes, then take a long time to commit. Meanwhile transaction B will start and commit, before A commits. The write from B will get a higher primary key than the write from A. If a client now asks for changes it will miss the still uncommitted write from A, and note the newest highest primary key. So even after A

I'm using git-svn. How can I get a list of what I've committed into git, but haven't yet committed to the SVN repository since the last git svn dcommit ? That is, how can I verify what is about to be sent if I do a dcommit? The --dry-run option for git svn dcommit is very useful for finding out exactly what will be committed to Subversion. In particular that has the properties that: It doesn't actually commit anything to Subversion It tells you which diffs will be calculated to create new revisions in Subversion It tells you which branch in Subversion you will be committing to - this is

What are git commit generation numbers ( hacker news link ) and what are their significance? VonC Just to add to siri 's answer , "Commit Generation Numbers" are: explained here : A commit's generation is its height in the history graph, as measured from the farthest root . It is defined as: If the commit has no parents, then its generation is 0. Otherwise, its generation is 1 more than the maximum of its parents generations. an old topic already mentioned at the creation of Git in 2005: Linus Torwald (yester, July 14th): Ok, so I see that the old discussion about generation numbers has