Stephen J. Turnbull schrieb:
Tres Seaver writes:
svn doesn't have any true tags, AFAIK: everything is a branch.
Yow! I couldn't have imagined that would be true. And didn't
It's not exactly true either. svn doesn't have either tags or branches,
it has only a single (directory)
Stephen J. Turnbull wrote:
I don't know about svn; I find it pretty painful to use for anything
but sequential tasking (update ... hack ... commit ... repeat). But
if you look at http://git.kernel.org/, you'll see a thicket of repos,
each of which probably contains a few to a few hundred[1]
* Will a DVCS allow simpler operation as if we are still using a
centralized system like CVS or Subversion?
Yes and no. There is nothing to prevent a formal workflow like that
in CVS/Subversion. However, the separation of commit into record
push to authoritative leaves open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georg Brandl wrote:
Stephen J. Turnbull schrieb:
Tres Seaver writes:
svn doesn't have any true tags, AFAIK: everything is a branch.
Yow! I couldn't have imagined that would be true. And didn't
It's not exactly true either. svn
Brett Cannon brett at python.org writes:
So my first choice for Mercurial fell through. If you would like to
represent Mercurial, let me know.
I can represent Mercurial, though it may be (more?) helpful if some of the
Mercurial-using python-dev regulars can occasionally step in.
Cheers,
On Thu, Nov 6, 2008 at 8:04 AM, Dirkjan Ochtman [EMAIL PROTECTED] wrote:
I can represent Mercurial, though it may be (more?) helpful if some of the
Mercurial-using python-dev regulars can occasionally step in.
I like mercurial, so I'll do this if I see something, but I don't use
it for anything
2008/11/6 Dirkjan Ochtman [EMAIL PROTECTED]:
Brett Cannon brett at python.org writes:
So my first choice for Mercurial fell through. If you would like to
represent Mercurial, let me know.
I can represent Mercurial, though it may be (more?) helpful if some of the
Mercurial-using python-dev
Brett Cannon wrote:
I have emailed some people who have shown allegiance to a specific
DVCS to seeif they are willing to fill in the usage scenarios for me
along with converting the dev FAQ so that we all have a clear way to
learn how to use the things. If any of the people I emailed turn down
On Thu, Nov 6, 2008 at 8:35 PM, Nick Coghlan [EMAIL PROTECTED] wrote:
I'd expect any DVCS to be able to handily beat what I currently do with SVN:
Yes, it does. I have extensive experience in bzr, less in git (but
vastly prefer it since I have been using it), and both are relatively
good for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
I disagree. This doesn't scale to Python size. For distributed VC to
work, somebody has to maintain a repo 24x7. Python has to do this for
the trunk; the additional burden for contributed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
You need not feel that way. It's not you---the flexibility of dVCS
means that until the Powers That Be promulgate a Workflow, this will
be ambiguous.
You're absolutely right. Adopting a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 6, 2008, at 6:35 AM, Nick Coghlan wrote:
If it isn't already there, suspending work on something to work on
something else would make a very nice scenario to cover, as it is
something even the core devs sometimes have to deal with.
Indeed.
Tres Seaver schrieb:
Georg Brandl wrote:
Stephen J. Turnbull schrieb:
Tres Seaver writes:
svn doesn't have any true tags, AFAIK: everything is a branch.
Yow! I couldn't have imagined that would be true. And didn't
It's not exactly true either. svn doesn't have either tags or
On Thu, Nov 6, 2008 at 06:23, Christian Heimes [EMAIL PROTECTED] wrote:
Brett Cannon wrote:
I have emailed some people who have shown allegiance to a specific
DVCS to seeif they are willing to fill in the usage scenarios for me
along with converting the dev FAQ so that we all have a clear way
On Thu, Nov 6, 2008 at 05:04, Dirkjan Ochtman [EMAIL PROTECTED] wrote:
Brett Cannon brett at python.org writes:
So my first choice for Mercurial fell through. If you would like to
represent Mercurial, let me know.
I can represent Mercurial, though it may be (more?) helpful if some of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 6, 2008, at 5:43 PM, Brett Cannon wrote:
On Thu, Nov 6, 2008 at 06:23, Christian Heimes [EMAIL PROTECTED]
wrote:
Brett Cannon wrote:
I have emailed some people who have shown allegiance to a specific
DVCS to seeif they are willing to
On Thu, Nov 6, 2008 at 14:52, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 6, 2008, at 5:43 PM, Brett Cannon wrote:
On Thu, Nov 6, 2008 at 06:23, Christian Heimes [EMAIL PROTECTED] wrote:
Brett Cannon wrote:
I have emailed some people who
Barry Warsaw wrote:
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
You need not feel that way. It's not you---the flexibility of dVCS
means that until the Powers That Be promulgate a Workflow, this will
be ambiguous.
You're absolutely right. Adopting a dvcs opens up a much
On Thu, Nov 6, 2008 at 16:47, Nick Coghlan [EMAIL PROTECTED] wrote:
Barry Warsaw wrote:
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
You need not feel that way. It's not you---the flexibility of dVCS
means that until the Powers That Be promulgate a Workflow, this will
be
Nick Coghlan writes:
If it isn't already there, suspending work on something to work on
something else would make a very nice scenario to cover, as it is
something even the core devs sometimes have to deal with.
I'd expect any DVCS to be able to handily beat what I currently do
with
Brett Cannon writes:
I consider that a perk feature.
Let's not judge which features are perks or essential quite yet. (If
the number of features/scenarios/whatnot becomes a burden on you, then
you must triage them, of course.)
But a lot of people will not know what the features are unless
Stephen J. Turnbull wrote:
In other words, *D*VCS is about keeping and (optionally) communicating
*local* history, not about reducing the number of VC-related operations
you do.
The bit I left out where it can get painful is when the patch call to go
back to the first task fails due to changes
Brett Cannon wrote:
I have started the DVCS PEP which can be seen at
http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
beyond the rationale, usage scenarios I plan to use, and what other
sections I plan to write.
Brett:
Would you care to get a PEP number allocated to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the second release candidate for Python 3.0.
This is a release candidate, so while it is not suitable for
production environments, we strongly encourage
24 matches
Mail list logo
