o have some hugin perl scripts here, the are from some websites but id like
to contribute with the group and contribute with the creator...

KFJ mind mailing the script?

On Mon, Nov 22, 2010 at 3:43 PM, Yuval Levy <goo...@levy.ch> wrote:

> On November 22, 2010 12:12:49 pm kfj wrote:
> > > If you don't have yet an SF user ID, open first a Launchpad account
> (and
> > > document it please).  Then you can use OpenID to log on and create an
> > > account on SF.  Theoretically it should be simpler than creating a new
> > > account from scratch.  I'm interested in a documented experience.
> >
> > You were right, I suppose. It was quite straightforward: I created the
> > openID
> > with launchpad. Then I just signed into SF with openID and I was at
> > the page
> > with my account details straight away.
>
> oh, wow.  and you grind your teeth about the documentation in the source
> code?
> [0] is the level of detail that I was hoping for.  Oh, well...
>
>
> > My SF user ID is 3139776
>
> It says "User does not exist" and I realize that I asked you for the wrong
> field.  When I look at my SF page it has a User ID *and* a Username.  It's
> the
> Username that I need, sorry.
>
>
> > I will need a bit of guidance concerning the actual upload, but I
> > suppose you can
> > tell me how to go on about that once you've made the SF repo, or send
> > me a link
> > to a description of the standard procedure?
>
> yes.  well, kind of.
>
> START:
> hg clone <REPO URL>
>
> you get the repo URL from https://sourceforge.net/projects/hugin/developand
> you can already see the scripts repo listed
> http://hugin.hg.sourceforge.net/hgweb/hugin/
>
> then the typical cycle is:
>
> hg pull     # to get get the latest changes
> hg up       # to update your local working folder with the latest change
> ...         # do your stuff
> hg ci       # from time to time, save your stuff to your *local* repo
> ...         # continue working
> hg status   # from time to time to check what has changed
> hg diff     # from time to time to check what has changed
> ...
> hg ci       # do a last commit before pushing
> hg pull     # pull in case there have been remote changes in the meantime
> hg up       # update if there have been remote changes.  hg will try to
>            # merge local and remote changes and will give an error message
>            # in case of conflict
> hg push     # push your local changes to the repo you pulled initially
>
> note that you must be internet connected only during hg pull and hg push;
> and
> that while hg ci "saves" a repo state in your local repo, it is still not
> backed up, i.e. if you loose your HDD, you loose all changesets since your
> last push.
>
> you may want to do some customization in your local ~/.hgrc file, like:
>
> [extensions]
> convert =
> hgext.hgk =
> [ui]
> username = YOUR NAME <em...@address>
> verbose = True
>
> that should be it. if you have questions, ask.  i know it should be better
> documented.  we have a wiki for that and every user is welcome to add
> there.
>
> Yuv
>
>
>
>
> >
> > with regards
> > Kay
>
> [0] <http://groups.google.com/group/hugin-
> ptx/browse_thread/thread/f0b37361d8eff283>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to