How to get all contribs from a specific person?

1 view
Skip to first unread message

Richard Cavell

unread,
Jan 8, 2012, 5:55:07 AM1/8/12
to us...@subversion.apache.org
Hi,

Is there some subcommand that will retrieve only those commits made by a specific person?  Currently I'm using:

svn log | grep Richard

Richard


Daniel Shahaf

unread,
Jan 8, 2012, 6:06:30 AM1/8/12
to Richard Cavell, us...@subversion.apache.org
No, but see contrib/client-side/search-svnlog.pl.

(And contribulyze.py can easily be hacked to generate such a listing, too)

Nico Kadel-Garcia

unread,
Jan 8, 2012, 11:27:38 AM1/8/12
to Daniel Shahaf, Richard Cavell, us...@subversion.apache.org

Good pointer.

May I note that top posting is frowned on in this list? And the
"contrib" directory has been reported here as going away soon?

Daniel Shahaf

unread,
Jan 8, 2012, 12:37:45 PM1/8/12
to Nico Kadel-Garcia, Richard Cavell, us...@subversion.apache.org
Top-posting is appropriate for short responses that address the entirety of the replied message.

Nico Kadel-Garcia

unread,
Jan 8, 2012, 3:31:33 PM1/8/12
to Daniel Shahaf, Richard Cavell, us...@subversion.apache.org
On Sun, Jan 8, 2012 at 12:37 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote:
> Top-posting is appropriate for short responses that address the entirety of the replied message.

Where does it say that? I'm looking at the guidelines at
http://svn.apache.org/repos/asf/subversion/branches/1.4.x/www/mailing-list-guidelines.html,
which include no such caveat. Admittedly, they also say that I should
not reflexively chide people for it, and I didn't think I did so
reflexively, but would welcome your opinion on the matter.

That sort of unstated exception is actually a problem for source
control, especially when used for QA. The guidelines for all sorts of
practices like backup and branching and regression testing are often
silently ignored in the field, because "we didn't need to say that" or
"this makes more sense" or one of my favorites from a conversation
last year, "just read the code". And then you don't know what actually
happened or what was done, which is anathema to source control or
testing environments.

Ryan Schmidt

unread,
Jan 8, 2012, 6:15:47 PM1/8/12
to Nico Kadel-Garcia, Daniel Shahaf, Richard Cavell, us...@subversion.apache.org
On Jan 8, 2012, at 14:31, Nico Kadel-Garcia wrote:
> On Sun, Jan 8, 2012 at 12:37 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote:
>> Top-posting is appropriate for short responses that address the entirety of the replied message.
>
> Where does it say that? I'm looking at the guidelines at
> http://svn.apache.org/repos/asf/subversion/branches/1.4.x/www/mailing-list-guidelines.html,
> which include no such caveat.

From that very page:

> There are even situations where top-posting is preferable — for example, when the response is short and general, and applies to the entirety of a long passage of quoted text. So top-posting is always a judgement call, and in any case it's not a major inconvenience even when done inappropriately.

The current published URL for that by the way is

http://subversion.apache.org/docs/community-guide/mailing-lists.html#top-posting


Torsten Krah

unread,
Jan 11, 2012, 4:39:15 AM1/11/12
to us...@subversion.apache.org
Some heavy weight "alternative" may be to index your repository with
viewvc (using svndbadmin) and using the query backend of the tool, to
find all revisions done by author "XXX".

regards

Torsten

Reply all
Reply to author
Forward
0 new messages