On Apr 18, 2011, at 19:51, Doug Claar wrote:
> rfc2822 section 2.1.1 specifies that “Each line of characters MUST be no more
> than 998 characters…excluding the CRLF.”
> (http://www.faqs.org/rfcs/rfc2822.html)
>
> commit-email.pl has no mechanism to check/enforce that; thus, a large checkin
>
rfc2822 section 2.1.1 specifies that "Each line of characters MUST be no more
than 998 characters...excluding the CRLF." (http://www.faqs.org/rfcs/rfc2822.html)
commit-email.pl has no mechanism to check/enforce that; thus, a large checkin
of many directories will create an email message that vi
There are plenty of templating and text replacement programs around. Why
not use one of them?
IMO, it's feature bloat to try to make svn do everything possible for every
person.
Do you really want a Copyright notice that reads "Copyright 2008-$Year: 2011
$ FooBar Inc"? I doubt it.
$ echo "Copy
On Tue, Apr 19, 2011 at 12:02 AM, Daniel Becroft wrote:
> On Tue, Apr 19, 2011 at 7:29 AM, Alex Vincent wrote:
>>
>> I'm currently in the process of updating copyright notices where I work.
>> To me, this is an ideal place for a SVN keyword:
>>
>> Copyright 2008-$Year$ MyCompany
>>
>> The SVN key
Semantically, that's a good question: does the keyword apply to a checkout
or a checkin?
I would personally expect the last checkin year. This reflects when the
file was last updated, which is what really matters in copyrights, as I
understand them. (IANAL, though.)
On Mon, Apr 18, 2011 at 3:02
On Tue, Apr 19, 2011 at 7:29 AM, Alex Vincent wrote:
> I'm currently in the process of updating copyright notices where I work.
> To me, this is an ideal place for a SVN keyword:
>
> Copyright 2008-$Year$ MyCompany
>
> The SVN keywords listed in the online documentation list Date, but it's far
>
I'm currently in the process of updating copyright notices where I work. To
me, this is an ideal place for a SVN keyword:
Copyright 2008-$Year$ MyCompany
The SVN keywords listed in the online documentation list Date, but it's far
too specific for a copyright. As an alternate, perhaps a special
Firstly, let me thank everyone for their help.
I was "hoping / wishing" that here was some simple command line instruction(s),
that I simply didn't know about, that would do the job for me.
It would appear, not in the way I had hoped.
Mark Cooke suggested that I use a hook script to maintain the
On Wed, Apr 13, 2011 at 3:27 AM, Gavin "Beau" Baumanis
wrote:
> Create a file with svn log
> (svn log --verbose > svn.log)
> Then grep / search the log for the file you're after.
>
> Is there not a more convenient way to do this?
Have you seen ViewVC?
/$
On Mon, Apr 18, 2011 at 01:46:15PM +0200, Stefan Sperling wrote:
> FYI:
>
> Following up to last year's svnday event, elego will again host
> a conference about Subversion on 18th of May 2011.
Correction: 19th of May...
> There will also be workshops the day before (on the 17th).
... and 18th.
FYI:
Following up to last year's svnday event, elego will again host
a conference about Subversion on 18th of May 2011.
The intended audience are professional Subversion users.
There will be several talks held by Subversion developers and users.
There will also be plenty of time for attendees to
> > On Wed, Apr 13, 2011 at 11:27:22AM +1000, Gavin "Beau"
> Baumanis wrote:
> >> I have been doing some work everyone's good friend Mr.Google.
> >> Every blog / article I read all said the same thing;
> >>
> >> Create a file with svn log
> >> (svn log --verbose > svn.log)
> >> Then grep / search
12 matches
Mail list logo
