Config for branch, not in branch

[Vincent LADEUIL]

>>>>> "Denys" == Denys Duchier <duchier at ps.uni-sb.de> writes:

    Denys> Vincent LADEUIL <v.ladeuil at alplog.fr> writes:
    >> But then, why bzr allows different emails for different
    >> branches ?

    Denys>  bzr  allows  different  "profiles"  to  be  used  for
    Denys> different branches.  For example, if you contribute to
    Denys> two different projects foo  and baz, you might have an
    Denys>  email  of  ladeuil at foo.org  for  the  first  one  and
    Denys> ladeuil at baz.org for the second one.

    >> Is email just a strange beast which cannot be versionned
    >> but need to be attached to a branch anyway ?

    Denys> Well, it doesn't need to be attached to a branch: it
    Denys> can be set in the [DEFAULT] section rather than in a
    Denys> branch specific section.

But  then  it's  not  usable   for  the  example  you  just  give
before. What  I was trying  to address was the  problem described
earlier in the  thread where you move you  branched directory and
suddenly your email is not correct anymore.

I  just quit CVS  days ago  because I  was tired  of its  lack of
renaming features and here we  have some kind of renaming problem
:-)

    Denys>  As  for  versionning:  would  it  break  anything  to
    Denys> maintain  ~/.bazaar under revision  control using bzr?
    Denys> I don't think so, but I could be wrong.

When I was  talking about versioning I meant that  if I check out
an old branch, then my old email can be restored accordingly, but
as I said it's a bit stupid if that email is not usable anymore.

May be this email problem is  not worth the effort to address but
I  wonder if  other  kind  of informations  can  suffer the  same
problems...

        Vincent