git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Brown <jeff@jeffandbetsy.net>
To: git@vger.kernel.org
Subject: tracking committer vs. author
Date: Mon, 25 May 2009 16:20:02 -0500	[thread overview]
Message-ID: <bbd12f0f0905251420l1ab63ca5y32589a4451064b9a@mail.gmail.com> (raw)

I have noticed that when we pull changes from non-committers into our
repo, sometimes meta information about who committed the change to the
repo is included along side info about who actually wrote the changes.
 For example, see
http://github.com/grails/grails/commit/8ac450c37d16b0468ba0f92d3008968fd6a41a75
and note that graemerocher has commit privileges to the repo but
ihotary does not.  ihatory's commit was pulled in by graemerocher.

The commit at http://github.com/grails/grails/commit/ff770359d152683d5794887cd743a10ce7d04501
was also authored by a non committer.  I pulled that change in myself
this evening.  Notice that there is no info displayed there to
indicate that I (jeffbrown) am the person who pushed that change into
the repo.

I don't know what was done differently for those 2 scenarios but both
of those commits were authored by folks who do not have commit
privileges to the repo at
http://github.com/grails/grails/commits/master.

I don't think this is a github issue.  If I am wrong, please let me know.

If I want to track not only who authored the commit but also who
pushed it into the repo (like you see at
http://github.com/grails/grails/commit/8ac450c37d16b0468ba0f92d3008968fd6a41a75),
what is the procedure for making that happen?



jb

-- 
Jeff Brown
SpringSource
http://www.springsource.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

             reply	other threads:[~2009-05-25 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 21:20 Jeff Brown [this message]
2009-05-25 23:28 ` tracking committer vs. author Julian Phillips
2009-05-25 23:40   ` Jeff Brown
2009-05-26  5:10     ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bbd12f0f0905251420l1ab63ca5y32589a4451064b9a@mail.gmail.com \
    --to=jeff@jeffandbetsy.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).