From: Chris Ball <[email protected]> Date: Thu, 24 Jun 2010 22:18:34 +0000
Chris,
Could you post your version of
$ python -c 'import libbe.util.encoding as e;
import libbe.ui.util.pager as p;
print e.get_encoding();
p.run_pager();
print e.get_encoding()'
UTF-8
UTF-8
Everyone,
This cross-posts my recent comment bea/275/725, which is
available by pulling my Git branch at:
http://www.physics.drexel.edu/~wking/code/git/git.php?be.git
git clone http://www.physics.drexel.edu/~wking/code/git/be.git
I imagine noone's noticed yet, hence the cross post.
Now that other people are working on the code, we should probably pick
one of our available notification options to use amongst ourselves.
Options I can think of:
0) Cross post activity to be-devel (e.g. this post)
+ We've been doing it this way so far.
- Tedious (but could be automated, see [2*] below)
1) Everyone use --repo http://bugs.bugseverywhere.org/ for BE bugs.
+ Syncing is very easy.
- Not distributed, you can only interact with the checked out branch.
2) Use the "subscribe" hooks for all activity (currently it's just
be-handle-mail).
+ Change notification is very easy.
- Requires some implementation still.
2*) Use "subscribe" hooks (as in [2]), but only subscribe be-devel.
+ Automates [0].
- We'd have to decide on blacklisting/whitelisting repos.
3) Gitorious merge requests.
+ No additional infrastructure.
- This is something BE should be able to handle internally.
Thoughts? Alternatives?
--
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpvSx7zPCKJn.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
