Guido van Rossum wrote:
>Help!
>
>What's the magic to get $Revision$ and $Date$ to be expanded upon
>checkin? Comparing pep-0352.txt and pep-0343.txt, I noticed that the
>latter has the svn revision and date in the headers, while the former
>still has Brett's original revision 1.5 and a date somew
[Guido van Rossum]
>What's the magic to get $Revision$ and $Date$ to be expanded upon
>checkin?
Expansion does not occur on checkin, but on checkout, and even then,
only in your copy -- that one you see (the internal Subversion copy is
untouched). You have to edit a property for the file where
[Guido]
> Help!
>
> What's the magic to get $Revision$ and $Date$ to be expanded upon
> checkin? Comparing pep-0352.txt and pep-0343.txt, I noticed that the
> latter has the svn revision and date in the headers, while the former
> still has Brett's original revision 1.5 and a date somewhere in June
Help!
What's the magic to get $Revision$ and $Date$ to be expanded upon
checkin? Comparing pep-0352.txt and pep-0343.txt, I noticed that the
latter has the svn revision and date in the headers, while the former
still has Brett's original revision 1.5 and a date somewhere in June.
I tried to fix th
[EMAIL PROTECTED] wrote:
> I went ahead and used Tim's note as the basis for a page on the wiki:
>
> http://wiki.python.org/moin/CvsToSvn
>
> It's linked from the PythonDevelopers page (a page of previously dubious
> necessity).
I have pretty much the same reservations against Wikis as Brett
Tim> Excellent suggestions! I have a few to pass on:
skip> These are precisely the things the Wiki would be good for.
I went ahead and used Tim's note as the basis for a page on the wiki:
http://wiki.python.org/moin/CvsToSvn
It's linked from the PythonDevelopers page (a page of pre
Tim> Excellent suggestions! I have a few to pass on:
...
Tim,
Thanks for the tips. As a new svn user myself, I find these helpful.
These are precisely the things the Wiki would be good for. They don't
prescribe policy. They help people in a general way to migrate from cvs to
svn mo
On Friday 28 October 2005 21:29, Tim Peters wrote:
> - Finding out what's changed in your sandbox. Use "svn status"
> for that. Bonus: in return for creating zillions of admin files,
> "svn status"
> is a local operation (no network access required). Do "svn status -u"
> to get, in add
Hello!
On Fri, Oct 28, 2005 at 09:29:09PM -0400, Tim Peters wrote:
> - Finding out what's changed in your sandbox. Use "svn status"
svn diff uses locally saved copies of files. This increases speed by
trading for the disk space. It also decreases net traffic; that's important
for those who ha
[EMAIL PROTECTED]
>> Though there's no svn/cvs cheatsheet there, you may also find isolated
>> tidbits in the Subversion FAQ:
>>
>> http://subversion.tigris.org/faq.html
>>
>> Just grep around for "cvs".
[Martin v. Löwis]
> In addition, you might want to read
>
> http://www.python.org/dev/svn.
Fred L. Drake, Jr. wrote:
> On Thursday 27 October 2005 14:16, Martin v. Löwis wrote:
> > I think I would request a separate address; I don't think I want to get
> > all webmaster email.
>
> I like the idea of a separate address as well.
Perhaps the radically named [EMAIL PROTECTED]
Cheers,
Ni
Fred> Are you suggesting that the key-deposit address be routed to the
Fred> webmaster crew? Most of the webmasters don't have the access
Fred> needed to deposit keys.
In fact, many of us on the pydotorg list don't have ssh access either. I
suspect the number of useful recipients is
On Thursday 27 October 2005 14:16, Martin v. Löwis wrote:
> I think I would request a separate address; I don't think I want to get
> all webmaster email.
I like the idea of a separate address as well.
> That address should probably include webmaster, though.
Are you suggesting that the key-d
Fred L. Drake, Jr. wrote:
> Mail to pydotorg doesn't allow posting from non-members; I watch for
> notifications for owner on that list and try to approve as quickly as
> possible, but it's a manual process just to get the mail through.
Ah, didn't know this.
> We should probably have a dedicate
On Thursday 27 October 2005 12:07, [EMAIL PROTECTED] wrote:
> Send your keys to [EMAIL PROTECTED] Unless you specify otherwise, your
> login will probably be "jim.fulton".
Mail to pydotorg doesn't allow posting from non-members; I watch for
notifications for owner on that list and try to appro
Jim Fulton wrote:
>> Can anyone point an old CVS/Perforce-Luddite at instructions for how
>> to use the new SVN repository?
>
>
> And can you remind us where to send our public keys? :)
[EMAIL PROTECTED] should work; you will get a confirmation when they
are installed.
Regards,
Martin
_
[EMAIL PROTECTED] wrote:
> Though there's no svn/cvs cheatsheet there, you may also find isolated
> tidbits in the Subversion FAQ:
>
> http://subversion.tigris.org/faq.html
>
> Just grep around for "cvs".
In addition, you might want to read
http://www.python.org/dev/svn.html
Regards,
Marti
Jim> And can you remind us where to send our public keys? :)
Jim,
Send your keys to [EMAIL PROTECTED] Unless you specify otherwise, your
login will probably be "jim.fulton".
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
Jeremy Hylton wrote:
> Can anyone point an old CVS/Perforce-Luddite at instructions for how
> to use the new SVN repository?
And can you remind us where to send our public keys? :)
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714
Jeremy> Can anyone point an old CVS/Perforce-Luddite at instructions for
Jeremy> how to use the new SVN repository?
Jeremy,
I'd never used Subversion until Barry grabbed the python.org web maintainers
by our collective ears and dragged us to the table with the kool aid. As it
turns out,
Can anyone point an old CVS/Perforce-Luddite at instructions for how
to use the new SVN repository?
Jeremy
On 10/23/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
> "Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>
> > I'd like to start the subversion switchover this coming Wednesday,
> > with a tot
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> I'd like to start the subversion switchover this coming Wednesday,
> with a total commit freeze at 16:00 GMT.
Yay! Thanks again for doing this.
Cheers,
mwh
--
[Perl] combines all the worst aspects of C and Lisp: a billion
different sublangua
I'd like to start the subversion switchover this coming Wednesday,
with a total commit freeze at 16:00 GMT. If you have larger changes
to commit that you would like to commit before the switchover, but
after that date, please let me know.
At that point, I will set the repository to read-only (thro
23 matches
Mail list logo
