New submission from Eric Kow <[email protected]>: 1 patch for repository http://darcs.net/releases/branch-2.5:
The context of this change is that old-fashioned repositories are on their way
out after Darcs 2.5.
As part of our deprecation homework, we should try to make sure the transition
happens smoothly, for example, by ensuring that as many repositories as
possible are upgraded before Darcs 2.8 is released.
The proposed banner looks like this:
*******************************************************************************
_______ Sorry for the wait! The repository you are fetching is using the
| | DEPRECATED 'old-fashioned' format. I'm fetching it as a hashed
| O O | repository instead, but this may take a while.
| ___ |
| / \ | It would be ideal if the repository maintainer could upgrade the
|_______| remote copy as well. The hashed format requires a Darcs 2 client,
but is otherwise compatible with existing old-fashioned branches.
Upgrading is easy with Darcs 2.4 and higher:
example.com $ cd repo-name
example.com $ darcs optimize --upgrade
*******************************************************************************
I imagine this could use some more thought. I had quite a few false starts
at http://hpaste.org/30232/more_forceful_upgrade_notice (with #darcs being
helpful to fix a lot of mis-thinking)
Elements in play:
* Big frowny face: Three ideas here: emotional feedback (old-fashioned
makes Darcs sad), apologeticness (Sorry for the wait), and mostly
high-visibility (a face might jump out at you more than yet another
banner, so to be used sparingly)
* Using users to get at repository maintainers: a past version of this
plus drafts, basically asked you to get repository maintainers to do the
upgrade (since you can't do it yourself). But this isn't necessarily
easy, so I've made the language a lot softer.
* Slight sell: upgrading is backwards-compatible and easy. I tried to
qualify the backwards-compatible a bit
* Upgrade example: I thought maybe concretely showing you not just the
command to run, but how you would actually run them could more sucessfully
convey not just how to do it (err, do I optimize --upgrade foo, or do I
cd foo; optimize --upgrade?), but also that it's easy (one command).
Sort of show rather than tell.
So it's just about maximising effectiveness in getting people to switch, and
preparing the ground so it will be relatively painless when we finally withdraw
old-fashioned, while hopefully not insulting/annoying users in the process...
Worth a shot? :-/
Mon Sep 20 13:33:03 BST 2010 Eric Kow <[email protected]>
* More visible old-fashioned to hashed notice.
This also talks about old-fashioned as being deprecated.
___________________________________________________________
This email has been scanned by MessageLabs' Email Security
System on behalf of the University of Brighton.
For more information see http://www.brighton.ac.uk/is/spam/
___________________________________________________________
----------
files: more-visible-old_fashioned-to-hashed-notice_.dpatch, unnamed
messages: 12590
nosy: kowey
status: needs-screening
title: More visible old-fashioned to hashed notice.
__________________________________
Darcs bug tracker <[email protected]>
<http://bugs.darcs.net/patch401>
__________________________________New patches: [More visible old-fashioned to hashed notice. Eric Kow <[email protected]>**20100920123303 Ignore-this: 614a280d5e6da1c5aebd4fc8b5dcc27f This also talks about old-fashioned as being deprecated. ] hunk ./src/Darcs/Commands/Get.lhs 203 debugMessage "Identifying and copying repository..." copyRepoHashed repository | hashUs -> do - putInfo opts $ text "Converting old-fashioned repository to hashed format..." - $$ text "*******************************************************************************" - $$ text "Fetching a hashed repository would be faster. Perhaps you could persuade" - $$ text "the maintainer to run darcs optimize --upgrade with darcs 2.4.0 or higher?" + putInfo opts $ text "*******************************************************************************" + $$ text " _______ Sorry for the wait! The repository you are fetching is using the " + $$ text " | | DEPRECATED 'old-fashioned' format. I'm fetching it as a hashed " + $$ text " | O O | repository instead, but this may take a while. " + $$ text " | ___ | " + $$ text " | / \\ | It would be ideal if the repository maintainer could upgrade the " + $$ text " |_______| remote copy as well. The hashed format requires a Darcs 2 client, " + $$ text " but is otherwise compatible with existing old-fashioned branches. " + $$ text " " + $$ text " Upgrading is easy with Darcs 2.4 and higher: " + $$ text " example.com $ cd path/to/repository " + $$ text " example.com $ darcs optimize --upgrade " $$ text "*******************************************************************************" copyRepoHashed repository | hashThem -> do Context: [Accept issue1951: add outside of current repository. Eric Kow <[email protected]>**20100908095448 Ignore-this: 5085d7647e9408ea7b5282e1cb0d1079 Regression between darcs 2.4 and 2.4.98.5. ] [TAG 2.4.98.5 Reinier Lamers <[email protected]>**20100905170906 Ignore-this: 848f746fa6a939cef069abe6722d4206 ] [Bump version number to 2.4.98.5 Reinier Lamers <[email protected]>**20100905170855 Ignore-this: dfb020e93dd32bb205f338a27862d42d ] [remove --index option from matchOneNontag because issue1926 Iago Abal <[email protected]>**20100901161448 Ignore-this: 5e3911031baa219dab159eb263a2a9cf Removed for 2.5 release to avoid showing options to the user that are not implemented. ] [Relax the hashed-storage dependency (to >= 0.5.2 && < 0.6). Petr Rockai <[email protected]>**20100824081630 Ignore-this: 754a9cb5d02cf8771df0905e976cc6e ] [Clean up trackdown --bisect documentation. Eric Kow <[email protected]>**20100830125530 Ignore-this: e51acdad91cb83ac6e06552a66f45e1b ] [Document GHC 6.10 dependency. Eric Kow <[email protected]>**20100825152443 Ignore-this: 9714d0bd6abd20a521b7f8f86be274f7 ] [TAG 2.4.98.4 Reinier Lamers <[email protected]>**20100823183505 Ignore-this: 8257375d159e0d5a8cb548c6374adf39 ] Patch bundle hash: 8de084255b24528240dbcaaf82be80138c0d8c50
unnamed
Description: Binary data
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
