[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 2541 -

From: Nuutti Kotivuori <naked_at_iki.fi>
Date: 2002-07-16 06:28:34 CEST

Karl Fogel wrote:
> Nuutti Kotivuori <naked@iki.fi> writes:
>> How do I view a log message, with the commandline client, that does
>> not contain _any_ changed paths?
>> 'svn log -v -r2541 http://svn.collab.net/repos/svn' does not cut
>> it.
> Oh, I see what you mean now.
> We have a no-op commit.
> Two questions:

One more, from me. Related of course.

> - Should we even allow such a thing? Or is the presence of that
> commit itself a bug?
> - Even if we always prevent no-op commits, should the log code be
> sensitive to that assumption, or should it work anyway?

- Would we want a way to get a specific log message just from that
  repository, without caring about paths?

I, for example, do say 'svn log -rHEAD' just to see what the latest
commit was. If I don't see anything, I change that to 'svn log -rHEAD
http://svn.collab.net/repos/svn'. And now there was a buggy border
case when even that didn't help. All I wanted to see was the latest
log message. After that, I often say 'svn log -r2500:HEAD' to see the
latest commit messages, now that I know what the head revision is and
if it was interesting.

This happens from work, where I don't have access to my mails. And, if
the commit mailer would be disabled, I'd bet you'd be doing the same
thing every day as well.

So I wonder - is there need for something more - or should I just get
into the habit of using the URL there always and be done with it?

-- Naked

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 16 06:29:49 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.