Great News !!! After one year of constant nagging we test mercurial

[Francisco Diaz Trepat - gmail]

Great.. All done except actual cvs import.

Some questions:

"Creating a shared repository is simple: Just initialise it in *repositories
* like every other repository. However, nobody will be able to access it
unless you grant them permission. To allow a user to access the repository *
~mercurial/repositories/<repos>*, create a file *
~mercurial/repositories/<repos>.allow* which contains his username (the one
from *authorized_keys*) alone on a line. "

1) I will not have permission to run anything on
/home/mercurial/repositories. If I want to create
MySuperMercurialRepository, I have to sudo hg init?

      a) cd /home/mercurial/repositories
   b) sudo mkdir MySuperMercurialRepository
   c) cd MySuperMercurialRepository
   d) sudo hg init
   e) MySuperMercurialRepository.allow (add users here)


Is this correct?

2) this is only possible to do locally, right? Or if someone would like to
create another repository (e.g. MyOtherAwesomeMercurialRepository) from
their workstation remotely they can?

Thanks,
f(t)

PS: I think that Netbeans Refactoring ==> Rename (on a class) does not
executes an hg rename. This is not confirmed yet, but I have done the
--follow and cannot see anything past rename.

On Fri, Jun 13, 2008 at 4:20 AM, Martin Geisler <mg at daimi.au.dk> wrote:

> Kai Grossjohann <kai.grossjohann at verizonbusiness.com> writes:
>
> > Francisco Diaz Trepat - gmail wrote:
> >> And finnally if a file is rename, all history is lost. Right? does
> >> this happen in all scms?
> > I'm surprised that Mercurial loses history across renames. Perhaps
> > someone in the know can clear this up?
>
> Don't worry, it doesn't! You indicate a rename with
>
>  hg rename foo bar
>
> and later
>
>  hg log -f bar
>
> will tell you the history of bar and foo. The '-f' flag makes
> Mercurial follow renames and copies. I think it is not enabled by
> default since it is expensive, but I'm not sure.
>
> The reason why you would want to tell Mercurial about any renames is
> to get help in merging later. If someone makes a change to foo
> (without knowing about your renaming) you want to have that change
> reflected in bar when you pull the change in. This happens
> automatically when you remember to mark renames like above.
>
> --
> Martin Geisler
>
> VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
> SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080613/88b54d43/attachment.htm