Showing content from http://mail.python.org/pipermail/python-dev/attachments/20070713/32c78875/attachment.htm below:
<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">Facundo Batista</b> <<a href="mailto:facundobatista@gmail.com">facundobatista@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2007/7/13, Barry Warsaw <<a href="mailto:barry@python.org">barry@python.org</a>>:<br><br>> with merges. This means the end of posting patches because instead<br>> what you would do is post the url to a branch that you published some
<br>> place. It means that branch can be kept up-to-date as its parent<br>> branch changes, so a new feature candidate need never get stale. It<br>> also means your new feature candidate is a first class revision
<br>> control branch, just as usable as the trunk, say. So it's much more<br>> powerful than trading patch files around.<br><br>More powerful, maybe, but also more limitating.<br><br>Do you still have the "patch" metodologie? How can you provide a patch
<br>if you don't have a place to publish the change?</blockquote><div><br>All DCVS's I looked at had a simple file export for 'changes'. It's diff + metadata, basically, which means it includes renames, directory mutation, changelogs, change-dependency information (which 'revision' it is based on, in effect) and whatever else the DCVS needs or wants. You can toss those around just like you can toss around diffs.
<br></div></div><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4